To view parent comment, click here.
To read all comments associated with this story, please click here.
As Hakum Lie mentioned, experimentation is good.
What is important is that content is still viewable in all browsers.
This is a constant battle, especially now that IE6 is out and also all these new fancy features and modern browsers exists. There is a big gap between what is supported in those browsers.
That problem will obviously remain indefinitely, but what is supported by all browsers that are in use keeps getting more and more.
Even Opera supports things other browsers do not support which was thought up by Opera. Which is normal.
Like:
http://dev.w3.org/csswg/css3-gcpm/
http://www.w3.org/TR/css3-gcpm/
http://dev.opera.com/articles/view/opera-reader-a-new-way-to-read-t...
And which is a good thing.
The time between public specifications and deployment of the implementation in Chrome is short though. Too short ? I don't know.
Google has many websites people use on a daily basis, thus obviously is a big responsibility. If they don't make it work for everyone, everyone will suffer, including Google.
WebM-on-by-default on Youtube has been in development for 1 1/2 years now and it is not yet deployed.
SPDY has been deployed on Google websites and in Chrome for 1 year now. Some things in the specification still needed to be changed (draft 3).
Is it to soon ? Or is development to slow ? With these 2 examples I don't think so.
It is abused quite a bit by developers,
You should really have a look at:
http://vimeo.com/16326857 at 21:00
The important part is:
"as long as they update the syntax when it changes"
Some people use things like Sass ( http://sass-lang.com/ ) to not have to type them themselves.
Here you can see how they do that:
http://vimeo.com/33647875
Not sure if that is the best example, but I'm sure you can research it yourself if you want to.




Member since:
2009-08-18
As for the vendor prefix ... Nothing annoys me more.
It is abused quite a bit by developers, go to Smashing Magazine and find one of their "top 20 sites doing coolest <something or other>" and check how many of those sites work in IE8 or even IE9, some won't even work correctly in Firefox.
Here is a good example from Zurb
http://www.zurb.com/playground/osx-dock
It won't work even in the latest Firefox, to be fair to Zurb ... this is only a bit of an experiment.