What I don't like: it depends on JS.
Using LESS or SASS avoids most of the problem this article talks about it, although the generated CSS will contain every vendor prefix. I'm not sure the difference in CSS filesize is worth using this solution.
Does anyone know of a server-side solution like this? Wouldn't be hard to vary the CSS output based on user-agent. Although you'd lose some caching benefits.
Using compass you just have to type:
+linear-gradient(color-stops(#c7def4,#d7eef4))
+box-shadow(rgba($ycolor9,.6) 0 0 4px inset)
+border-radius()
http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#ex...
Have you?
Are you saying it’s not necessarily slower to use JS to generate CSS on the client-side, compared to just serving up the CSS with all prefixes included in the first place? Do we really need a test case for that? I’m not even talking about your code or anything; just the general idea.
In general, it’s a bad idea to rely on client-side JavaScript for something that can be done without. PrefixFree is no exception.
I can see how PrefixFree can be useful for quick demos or during presentations (the way you use it is awesome!) but when you’re gonna post an article like this on a site like Smashing Magazine _people are gonna use it_ in production as well.
I love your work Lea, you know I do; I just don’t agree with the philosophy behind this particular project.
Stylesheets are cached and a one-time hit for new visitors - this method has to reiterate on every single page load.
Use LESS and precompile your CSS... it will change your life.