Disappointing article, given all the other ways in which Chrome is harming the web. Example: There's a bug on a site I made in Chrome. It is categorically incorrect behaviour on the part of Chrome, it breaks the specs in order to be faster. How do I fix the bug? By calling a proprietary interface in Javascript that only exists in Chrome. Yup, that's right - to make my standards-compliant web page work, I have to do browser-specific stuff for Chrome. It actually works fine in Internet Explorer 9, and has no IE9 (or 8 or 7) specific code in it. This is actually the second time that Chrome has been the stand-out browser for causing issues when building a site (unless you count Opera - I don't).