3 ms·

I agree it's better than what we had before, but... 1. Basically now we're stuck with +five lines to specify one thing. When can we switch to just one line, an

I agree it's better than what we had before, but... 1. Basically now we're stuck with +five lines to specify one thing. When can we switch to just one line, and drop the prefix versions? I doubt any time soon. We're only now dropping support for IE6. 2. how useful is it to be able to build stuff that only works in some browsers? I get that it helps push stuff forward, but you get myriad posts on HN that are like "look at this sweet thing I built (only works on chrome)" or something similar. Good for you, you built something cool, but you might as well have done it as a native app because I can't run it without downloading a different browser. Interoperability is one of the basic premises of the web.

Groxx 15y ago
Which is why many projects have moved beyond writing such things by hand, and use css-compilers. And interoperability is never one of the premises of the bleeding edge, which is generally what those myriad posts touch on (HTML5 audio, for example). Many of the older CSS3 specs are now supported in modern browsers, so I'd say we're pretty close, really. Or now, if you only support the most recent version (which accounts for what, >50%?). A stupendously far cry from where we used to be not too long ago.