to me the real issue is not so much the format. its standardization. (standard-issue stack-based VM) - no two javascript VMs support the same things. - no two

to me the real issue is not so much the format. its standardization. (standard-issue stack-based VM) - no two javascript VMs support the same things. - no two HTML engines support the same things. - no two CSS engines support the same things. So there you go, dear open and standard web: you're not. you're just not standard. it's time for people to realize that. There's a zillion w3c drafts which every browser attempts to support, and they spawn new ones (hi Google) all the time. There's zillion of new extensions to solve "HTML5 stuff that we need" (everything is called HTML5 if its new features, easy!) and of course many are not compatible, or implemented only by one or the other browser (audio stuff, database stuff, etc). And you have pages with "works best in chrome" or even "you need chrome to see this". Chrome is the best example because Google is the company coming with the most new drafts and the most "Chrome-only" technology. But it could be other companies eventually. Well again guess what. That's not standard. At all.