July 06, 2004
1996 all over again...
Posted by bopuc at July 6, 2004 03:30 AM
I was thinking about writing about this but Tim Bray brought it up (and is in a better position to do so...)
ongoing · Party Like It's 1996!
I'm a major admirer of Safari and of its primary author Dave Hyatt. But a couple of Dave's recent notes have caused me serious discomfort. Here he notes that Safari will support a new
search=attribute on theinputelement, and here he discusses a newcanvaselement. Even more troubling is the opening phrase: Another extension we made to HTML is... I'd be really happy if someone explained to me how this is different from what Netscape and Microsoft did to each other so irritatingly back in 1996 (<MARQUEE>anyone?). What the W3C and Web Standards Project were created to stop? [By the way, there are namespaces, there areclass=attributes, there are legitimate ways to extend HTML.] Someone please explain to me why I'm wrong, because I really hope this isn't what it looks like.
My thoughts and concerns exactly...
Comments
My understanding is that these extensions are primarily intended for Dashboard - Webcore has extended HTML to allow wid/gadget authors to have greater control over the way widgets display and work.
It is not clear that these extensions are intended to extend Safari's capabilities in a proprietary manner, or confer a competitive advantage to Safari.
Posted by: diskgrinder at July 6, 2004 05:00 AM
If it's implemented, it will be used.
If it's used, it will damage interoperability.
The standardization has a cost: slow, painful, consensus.
The benefits of standardization: Social freedom. You can use the tools without to worry of what you have to use, the cost of it, etc, you give the freedom of choice to the user.
Tim Bray is right. What's happening is dangerous.
Posted by: Karl at July 6, 2004 11:29 PM
Thanks Karl. Exactly.
"It is not clear that these extensions are intended to extend Safari's capabilities in a proprietary manner, or confer a competitive advantage to Safari."
It's irrelevant what the intent is. It contravenes standards, standards that were VERY long in finally being recognized and respected.
That said, this is built into Apple's WebCore. Let's hope it is disabled in Safari, at least.
Posted by: Boris Anthony at July 6, 2004 11:52 PM
Look at it this way: There are a few real-time compositing graphic languages: DisplayPostscript/Quartz, QuickDraw, OpenGL. Apple is adding a new one: HTML/CSS/JS. This isn't about extensions for the web, it's about giving Mac developers the ability to composite on screen in a highly accessible language.
This is for the Mac Platform, not the Web Platform.
See more on this at my Journal: http://www.bad-seed.org/dwelling/
Posted by: Ross Olson at July 7, 2004 03:55 AM