Break Free From CSS Prefix Hell • Hacker News Board

Re: Break Free From CSS Prefix Hell

#11

Post by samgro » Wed, Oct 12, 2011, 6:12 PM UTC

bretthopper wrote: post #2

What I like: it detects your browser and only sets the needed prefixes. 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 o…

SASS @extend solves most of the code bloat - if you have lots of elements styled with border-radius: 5px, using @extend, the vendor prefixed code will only appear once in the compiled CSS.

http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#ex...

Re: Break Free From CSS Prefix Hell

#12

Post by jewel » Wed, Oct 12, 2011, 6:20 PM UTC

bretthopper wrote: post #2

What I like: it detects your browser and only sets the needed prefixes. 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 o…

I imagine that if the generated CSS is gzipped the vendor prefixes compress well, since they are quite repetitive.

Re: Break Free From CSS Prefix Hell

#13

Post by mathias » Thu, Oct 13, 2011, 5:06 AM UTC

leaverou wrote: post #9

mathias wrote: post #6

When did we stop caring about FOUC and client-side performance?

FOUC? It's only some CSS3 that won't display until DOM load, not the whole styling. As for the performance, I'm pretty sure you're just guessing, and haven't done any testing.

> As for the performance, I'm pretty sure you're just guessing, and haven't done any testing.

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.