Above is the PDF from today’s talk. I had a good (but unfortunately truncated) discussion with Aaron Gustafson afterward, and it appears that there are those on the standards advocacy front who understand that those of us who “just make it work” for a living aren’t evil and want exactly the same things. Hopefully this will open up a broader discussion (although I suppose that posting something on a blog hardly counts as “discussion”).

One Comment
The PDF seems damaged. I get:
xpdf Desktop/dojostandards_heresy.pdf
Error: PDF file is damaged – attempting to reconstruct xref table…
Error: Couldn’t find trailer dictionary
Error: Couldn’t read xref table
XtUngrabButton(drawArea,3,0)
Warning: Attempt to remove nonexistent passive grab
and
evince Desktop/dojostandards_heresy.pdf
Error: PDF file is damaged – attempting to reconstruct xref table…
Error: Couldn’t find trailer dictionary
Error: Couldn’t read xref table
Error: PDF file is damaged – attempting to reconstruct xref table…
Error: Couldn’t find trailer dictionary
Error: Couldn’t read xref table
I downloaded twice to check. HTH Stuart
3 Trackbacks
[...] Alex just posted slides from his recent talk on Web Standards and how they help and our hurt the web in general. Definitely worth a look. [...]
[...] In perhaps the most intellectually-stimulating session at The Rich Web Experience, Alex Russell (of Dojo Toolkit fame) tackled the topic of Standards Heresy. [...]
[...] In my “Standards Heresy” talk I noted pretty bluntly that CSS 3 is a joke. A sad, sick joke being perpetrated by people who clearly don’t build actual web apps. If the preponderance of the working group did, we’d already have useful things like behavioral CSS being turned into recommendations and not turds like CSS namespaces and CSS Print Profile. And I’m not even sure if the “Advanced” Layouts cluster-fsck can should be mentioned for the fear that more people might actually look at it. You’d expect an “advanced layouts” module to give us hbox and vbox behaviors or a grid layout model or stretching…but no, the “answer” apparently is ascii art. No, I’m not making this up. It’s sad commentary that you can propose this kind of dreck at the W3C and get taken seriously. [...]