Why are we all blogging and talking about HTML5 and how it’s almost here? HTML5 is old news and became known in production environments back the first half of 2010...
So far, Google appears to be the only well-known corporation pushing for the web based industry to move forward and advance toward developing by standards, rather than 10 years behind them. We, as developers, should no longer be spending long nights testing clients web content in multiple browser. It’s time to utilize our resources and time towards the progress and advancement of the content we design for our clients, rather than restoring or repairing cosmetic defects with non-compliant or legacy browsers. I, along with many others, currently refuse to support, restore, or repair content issues in relation to legacy browsers. The presence of other bloggers posting similar opinions isn’t hard to find, some have went even so far as to post examples of how to block IE6 entirely or reduce functionality to the user based on the incompatibilities of legacy browsers.
I promise I will fire my next client as a customer who insists on providing support for legacy browsers. I make this promise to myself and on behalf of all other developers who cry themselves to sleep over the matter, as I know I once did. This blog actually breeches the scope of legacy browsers and actually covers my opinion on legacy use entirely. Providing primary support for legacy users is promoting the use of legacy systems or equipment and hinders the technical industry as a whole. Do you even know what the word “legacy” means, when referring to electronics? A legacy system is basically an old system that users still use even though better alternatives have been adopted that are more effective…
As I’m ending this article I want you, whoever you are, to think about a few things. As a client who wants a good website designed by a good developers, asking him to support legacy systems can, will, and should cost you more. Supporting legacy systems can and will hinder the functionality of your site, and will cause your developer to spend time in areas that he/she shouldn’t be spending time in, inhibiting them from spending time in the most important areas; Insuring functionality in supported and standard accepting browsers, as well as cosmetics. Developers, you will spend many a sleepless, underpaid, and frustrated night trying to support legacy, non-standard, and old browsers, set yourself free.
No comments:
Post a Comment