#366 - Drop legacy support
| Identifier | #366 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Drop legacy support |
| Status | Completed |
| Tags |
Risk: Deprecates functionality (custom) |
| Handling member | Chris Graham |
| Addon | core |
| Description | Drop lots of legacy support...
Anything less than MySQL 5.1 Anything less than IE8 (but no promise of the coolest UI features on anything less than the latest generation of browsers) Anything less than PHP 5.2 |
| Steps to reproduce | |
| Additional information | Update our coding guidelines, our requirements (on website and docs), tidy up CSS and JS to remove hacks (e.g. setOpacity should not be needed, or the PNG hack, or re-definition of file_get_contents). |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
Drop the dead weight of old technologies.
Right now, the world is changing so fast making the costs of keeping with the old ones prohibitive. IMO developers and admins of modern CMS must make a choice between pleasing all of the potential users or moving forward with exciting innovations supported by modern browsers to attract knowledgeable members and keep websites on the edge of what's invigorating.
I have had to disable a lot of the graphical wizardry just to get my pc to start-up at all. :(