Feel free to read through my post history if you really want to question my intentions. By the way, I also built a TechStars company that automated the detectio

Feel free to read through my post history if you really want to question my intentions. By the way, I also built a TechStars company that automated the detection of rendering issues across different browsers, I've written BHOs for IE6 - IE10, I'm a core Selenium developer, and I wrote the code that does screenshots for the IE driver in Selenium. I have a pretty good grasp on browser technologies and their timeline. Yes, I've encountered sites & apps that require the absolute latest version of Chrome, which is on a 6 week update schedule. I've tested 10s of thousands of different sites. You really don't need to quote parts of that and then tell me it's not the point. So, let's just assume for a moment that I'm not lying, and by some miraculous sequence of events your life experiences ended up being different from mine. Given all that, my question still stands. What's the point of a standard if it's a constantly shifting target, developers target it and they lock you out if you're not running the latest version of a specific browser? Placing IE6 in the context I clearly outlined, where it was an actively developed browser and considerably better than Netscape on SeaMonkey... how is what MS was doing any different than what Google's doing now? Both see the standards bodies as being too slow to act, so they roll out their own improvements, devs adopt them and lock out others. The only difference I can really see is MS only documented their changes, rather than creating a competing standards body à la WHATWG. That may even be the best thing for progress. Even during IE6's active period, it's how we ended up with technologies like Ajax. But being an "open standard" is meaningless when it only runs on one constantly shifting target. That's the world we're converging on again because it's convenient for developers to do so. Side note: You and I are obviously talking about two different classes of web devs. The ones I'm talking about, constantly adopting new technologies and locking out everyone else, gave up on IE6 long ago. Many of them don't run Windows and have never built a site that works on anything other than a Chromium-based browser.