Linked by Thom Holwerda on Tue 24th Mar 2009 23:26 UTC, submitted by inkslinger
Thread beginning with comment 355231
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Some standards should of course be adhered to, and the ones you mentioned are decent examples. But everything in Acid3? Sometimes I feel that many developers do frilly stuff like that just because they can, not because they should.
I'm with MS on their decision...the entire kitchen sink approach just isn't worth it.
Some standards should of course be adhered to, and the ones you mentioned are decent examples. But everything in Acid3? Sometimes I feel that many developers do frilly stuff like that just because they can, not because they should.
I'm with MS on their decision...the entire kitchen sink approach just isn't worth it.
I'm with MS on their decision...the entire kitchen sink approach just isn't worth it.
I cannot side with Microsoft here, as long as they leave important pieces of the puzzle out (SVG) while offering incompatible own implementations to improve vendor lockin (Silverlights vector graphics which were clearly derived). We are not talking about kitchen sink here, but something along the lines of being able to display real vector graphics.




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