While I’m not a huge fan of Internet Explorer, I am quite impressed with the progress the IE team has made. IE7 stands to be the most impressive release so far, with many rendering issues resolved, rather impressive security advances, and a great many improvements on the standards compliance front. I must applaud both the team, and Microsoft for making these moves.
By focusing on standards, instead of proprietary features that degrade the experience for everybody, developers can work towards a unified web, free of browser discrimination and hack filed code. It seems like the Redmond power house has finally started to see where IE needs to go to remain relevant for Web 2.0, and beyond.
Then again, that’s leaving TIME out of the picture.
Time up for TIME?
While HTML + TIME could prove to be a fun toy, due to its very nature – it’s a toy not everybody could enjoy. This is an older (introduced with IE5), proprietary technology that is fairly unknown, and not often used. While it does have some merits in its concept, any design technology that is intended to serve a single, closed platform is simply a bad idea.
Why Microsoft is taking another look at this, I’m really not sure. I’m holding out hope that they are cleaning up old, non-standard features in preparation for the next release. My fear is that they want to make another push with this out-dated, IE-centric technology.
Holding out hope…
Let’s hope they make the right call, and remove support for proprietary ‘features’ such as this. IE7 has the chance to not only catch up with the other major players, but to help push the wide-spread adoption of standards compliance.
If you enjoyed this article, please consider sharing it!
I guess you missed the part where it said HTML+TIME is based on SMIL 2.0 (a W3C standard)… (Then again I don’t know how closely it matches the spec.)
Hoopskier,
Actually, I did notice that part. My concern is that in building on top of a standard, you still end up with something that is intended to serve only the users of a single platform (IE in this case).
If HTML+TIME was to be submitted to the W3C, for review as an extention to SMIL 2.0, then I would have no issue with it. Now, it’s very much possible that I’ve missed something here, but as of yet I’ve not seen a sign of Microsoft moving towards submitting this as a standard.
I understand that it’s hard to develop and submit new technologies for standardization without working implementations, yet one must be careful about pushing these non-standard technologies for use in production environments.
It’s all too easy to become dependent on something like TIME, which is not yet supported in other platforms. This leaves many people out in the cold.