In this article, I will look at some of the misleading arguments used to promote Web Standards.<\/p>\n
Before I jump into this, I would like to point out a few things:<\/p>\n
– –<\/p>\n
<\/p>\n
THE WEB STANDARD’S MYTHS<\/strong><\/p>\n Myth #1: Web Standards equals less code – so you will have faster loading pages and you will save money on bandwidth.<\/strong><\/p>\n Theoretically this could be <\/strong>true, but consider these points:<\/p>\n The examples used (by Web Standards zealots,) to promote the bandwidth and cost savings argument are not realistic; sure, saving 10k-20k a page might make a difference for one of the most popular websites in the world, but most of us will not be working on such huge projects.<\/p>\n From a practical point of view, it is likely that you will never see any real benefit (in terms of bandwidth and speed) with having less code in your pages. <\/p>\n The truth: <\/strong><\/p>\n Less code in your pages is a good thing – because this means less work.<\/p>\n In the programming world, people are moving more and more towards languages and frameworks that diminishes the amount of code needed to get the job done. <\/p><\/blockquote>\n That being said, you can build ‘old-style’ websites that are ‘code efficient’ as well. As such, this code argument has much more to do with good practices and not whether you are adhering to Web Standards or not.<\/p>\n Targeting code to reduce file size, is like being concerned (if you want to loose weight) about the sugar in your coffee at McDonalds … what about the super-sized Big Mac trio?!<\/p><\/blockquote>\n Myth #2: Your websites will be forward compatible.<\/strong><\/p>\n The forward compatibility argument implies that if you have an ‘old style’ website that one day the browser makers will suddenly stop supporting them.<\/p>\n This is very unlikely since they (browser makers,) don’t have a history of removing functionality – they probably don’t want to kill the tens of millions of web pages that are built using ‘old-style’ techniques.<\/p>\n That’s one of the reasons we have doctypes, this allows browser makers to have several ‘engines’ that can parse pages whether they are Web Standards compliant or not. <\/p>\n\n