Yorgo the barman had a friend drive us to Zeitgeist where there was THE TAMALE LADY and I had tamales and chocolate and Guinness and rum and YOU ALL MISSED OUT ON THE GREATEST FUCKING NIGHT IN SAN FRANCISCO EVER AND I LAUGH AT ALL YOUR MISFORTUNES! That is, until tomorrow morning, at which point I will likely be in heavy Regret Mode. -- Crackmonkey
Ever try to make a commercial Web site? Then you know what
kind of a royal PAIN IN THE ASS it is. You spend 20% of
your time doing the real meat of the site, and 80% doing
this-doesn't-look-quite-right in Fuckhead Navisplorer
four-dot-my-dot-ass. I HATE that!
The most gruesome part is that there's all these goddamned STANDARDS for this
kind of stuff. Like HTML 4.0, CSS 1 and 2, XML, and ECMAScript (the
disease, but it's a programming language). There are TEST SUITES and REFERENCE
IMPLEMENTATIONS up the ass -- and yet, none of the three major browsers comes
even CLOSE to working well with these technologies. GAR GAR GAR!!
It's a FUCKING STRUGGLE to use the Web. I HATE it. It's BULLSHIT. But maybe,
just maybe, groups like Web Standards can put the HURTING on the browser
vendors to conform to the goddamned standards.
WebStandards.org is an advocacy group. They've got a real simple baseline
request to browser makers: support the above-mentioned standards. That's it.
It's not HARD to DO. The CODE is out there! Man, what's such a fucking big deal
Sure, there are other things you can do to get these standards well-recognized.
Contributing code to Mozilla would be good.
Writing clever, angry commentary in Webzines helps, kinda. But really, giving
the vendors a clear message is the best way.
Because it's not supposed to be this hard -- it's really not.