The browser wars are over. The market is being dominated by boring standards-compliance. The dominant leader is so comfortable with its position that it's tossing a bone to its competitors by reducing the extent to which the product is tied with Windows. Netscape ahs been available for a year and doesn't seem to have a hope or a prayer of surpassign Netscape 4 in market share.
And the browsers are stagnating. While the W3C certainly hasn't slowed down - it's making more recommendations than ever before - the browser companies have. I recall the dawn of Internet Explorer 3 - it was revolutionary. Although I wasn't completely sold on this whole 'css thing' at the time, I thought it was 'kinda neat'. Well, it's taken five years for Microsoft to implement those CSS standards. The implementation is the centerpiece of an otherwise lackluster version upgrade - the sixth edition of Internet Explorer. How long it takes to acheive complete CSS2 support (and whether that's even a desirable goal) is up to interpretation. What isn't is that the pace of innovation on the part of Microsoft's Windows Internet Explorer team has slowed considerably. This showpiece product is not only being shown up by the IE Mac team, but it's also being superceded by the open-source Mozilla and the ever-so-small Opera. Microsoft is falling behind and they know it won't matter for the sake of their market share.
For end users, the additions are similairly lackluster - the automatic resizing of images as the major bullet point? Excuse me. This is a problem because it creates no insentive for users to upgrade to the most recent release of the browser. As such, Microsoft's decision to follow the standards route is a lot less incredible if this is the last standard they'll implement for years to come. The pace of onnovation seems to have slowed to the point where adding a couple of CSS features is considered good.
Will the day ever come when we start to see CSS3, SVG, full XSLT/XML support and the like in Internet Explorer? Sure. Will it come soon? Not bloody likely ...







- Dreamweaver has the best support for DHTML of any WYSIWYG so I'm not sure I understand your Microsoft-dhtml vs. Macromedia-others distinction.

Bookmarks