Linked by Thom Holwerda on Tue 24th Mar 2009 23:26 UTC, submitted by inkslinger
Permalink for comment 355231
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-17
The ones mentioned like PNG, SVG 1.2 (or 1.1/1.0)?
I haven't met anyone "in the real world" who isn't about standards for a while, about 3 years. Maybe I'm not in the same environment as you.
"In the real world" standards save time, and because time is money it saves money too. It means with the exception of IE, I can trust that my site will work (with about 99% certainty) on the next iteration of their browser engine. And here's a kicker, I charge extra on a monthly fee for testing when new browser versions come out. It's about keeping the site updated.
"In the real world" it's really important that browsers implement these standards correctly and keep up to date with new ones to push the web forward, not their own agenda.
One thing I don't see mentioned as a reason for implementing drafts of standards with specific tags is so developers can start testing them before using them on live sites. As more developers test the more likely a glitch will happen. The more likely a glitch is found before real world implementation of the spec, the less likely it will hinder the web.
It's like a beta period before implementing the real thing.
Edited 2009-03-26 18:42 UTC