| This seems a little premature. It's the first build. The problem with these grids or "tests" (like the Acid3) is that they are being used to prove a point - but they fall short of the real goal - showing what is agreed to be implemented and has been implemented (the Acid3 test written by Google's Ian Hickson hasn't removed the W3C non-recommended SVG fonts). - The W3C chose IndexedDB over Web SQL so it's no wonder IE10 doesn't support it. - Mozilla has been working on WebGL for years now (piece by piece?), and Chrome just got it very recently (is it complete?). - Web Sockets, wasn't that disabled for security reasons until a fix is found? - Chrome is considered the pinnacle in this blog post and yet there's no mention of ECMAScript 5. Chrome's development started in secret and took some Mozilla engineers in the process and even though Chrome is mostly developed out in the open, Crankshaft (new V8 engine) and WebM were not. I'm not going to say IE hasn't been marketed a little bit unfairly, but I think a little transparency should be welcomed no matter who it is. Remember all businesses present incorrect facts to benefit (I'm merely stating, not excusing), an example being Chrome never actually downloading the web page in the promotional video a while back, it rendered from a local file. You're welcome to correct me if I'm wrong. |