#366 - Drop legacy support

This is a spacer post for a website comment topic. The content this topic relates to: #366 - Drop legacy support
Oh Yes!
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 completely agree with Jean. Even lag-about Microsoft is finally seeing to it that their browser is brought up to modern technologies. I want to see Composr built for the future, not for the past.
What about support for older versions of Firefox,dev versions of google chrome,etc....?Using this portable version of Google Chrome:16.0.896.0 (Developer Build 103424 Windows)

The policy has always been to only support the latest versions of browsers other than IE. This is because IE is the only one that does not auto-update, and most other browsers are installed by people by choice (so they know how to keep up to date).
I haven't updated firefox in ages due to the fact that my pc is badly messed up and newer versions have graphical acceleration which my onboard graphics card won't be able to handle.I still use firefox v3.6.16.

I have had to disable a lot of the graphical wizardry just to get my pc to start-up at all. :(
Unfortunately, time moves on and, so too, must Composr.
Thanks for your sponsorship, Jean. Just 5 more credits to go till we help Chris move Composr's foundation to a more modern base.
I have implemented the front-end part of this with the sponsorships here, and put the server-side stuff into another issue. That stuff is less interesting anyway, and easier for us to sort out later too.
0 guests and 0 members have recently viewed this.