Microsoft promises IE web-standards love
Developers, we're listening. Promise
Repairing past ways
It would be easy to see this as prevarication on the subject of SVG by pointing to the infinite number of sub specs and by playing a bureaucrat's card of citing the complexity of the process as a reason not to act. In this case, the burden of delivering a complete test suite to evaluate compatibility in as many different scenarios as possible for each and every spec.
According to Hachamovitch, though, Microsoft is repairing its past ways.
"In the '90s we though about: there's a spec and an implementation and all we need are two implementations, and if they work the same way, then that's good enough. But that's not good enough for developers, because there are two implementations but how do you know you've hit all the [test] cases," Hachamovitch said. "Going through and developing a complete test suite is responsible engineering."
Why this conversion to standards in IE 8 in the first place, when Microsoft could easily have continued bending web developers to its will using the force of its market share? Hachamovitch reckoned the world changed and that Microsoft saw this change coming. With IE 5.0, 5.5, and 6.0, the specs were "not full formed" and people weren't really using CSS.
"What changed was developers pushed the limits and developers got much more facile with the standards...in '05, '06, and '07 as people pushed the boundaries their expectations went up."
Some would agree Microsoft saw the world changing, but with the rise of things like XML and web services, saw the prospect of its power and relevance slipping away as developers began working across compliant browsers. Such a future would have seen the pool of new applications and resources for IE and Windows dry up.
Hachamovitch agreed Microsoft didn't have an option but to change. He just didn't quite go along with our thesis. "We said 'OK, we need to do right and finish out these more accurate and more faithful implementations,'" he said.
It was telling at Mix that Hachamovitch made repeated references to the amount of research Microsoft had done in studying users' browsing habits to explain the building of new features and functionality in IE 8. This is something Microsoft's been doing a lot on Windows 7, which will support IE 8 in the next code drop, Hachamovitch said during a meeting with press.
On features, though, the supposedly loyal Mix crowd appeared a little underwhelmed on IE 8. Some saw the browser as catching-up to rivals - particularly on having sandboxed sessions for tabs to help protect against crashes, and that are also found in Chrome. Digging deeper, it turned out, you only get separate sessions for three tabs - after that tabs start sharing again.
Hachamovitch reckoned that among Microsoft's data it found "most people" settle at three tabs, so IE 8's been "optimized for most common processes".
These are not good portends for IE 8. Most users don't care what browser they are running, which means it comes down to persuading developers to promote the browser via partners and add-ons.
Asked how he hoped to differentiate IE 8 against Firefox, Chrome, Opera, and a renewed Safari on Windows, Hachamovitch said Microsoft can gain by arguing the "real benefits" of IE 8. He inevitably pointed to things like the browser's click-jack protection, prevention of cross-site scripting as standard, performance, and the addition of Web Slices and Accelerators.
Interestingly, though, Mix Twitters dinged Microsoft for cherry picking features to make IE 8 "look good" while others thought Hachamovitch had been unfair on Firefox during his keynote. ®
Sponsored: Hyper-scale data management