3 ms·
I'll jump in, because I spent six months developing a web app using Sass. It's a nightmare to maintain on any sort of complicated, big project. For various reas
by anatoli 18y ago
I'll jump in, because I spent six months developing a web app using Sass. It's a nightmare to maintain on any sort of complicated, big project. For various reasons... I previously blogged about it here: http://fecklessmind.com/2009/01/28/fuck-sass/ http://fecklessmind.com/2009/01/28/fuck-sass/
Ultimately, yes, you can use whatever the hell you want. But if you're a front-end developer, if you care about your webiste scaling to millions of users, if you care about providing best experience even to dial-up users or users of old PCs / Macs, then you're going to spend the time optimizing everything you can. Sass goes against that and creates bloat. Fine for back-end developers who just want the pain of working with CSS to be over, maybe, but not for front-end developers.
Haml on the other hand is great.
- psadauskas 18y agoWhere's the bloat? As mentioned a couple comments up, you can have Sass render the css into a single line CSS file for production. And you render it once, and cache it forever. Same overhead as a css file, maybe even less, because it's auto-minified for you...
- chriseppstein 18y agoSass doesn't make you bloat your css, but it does make it easier if you rely heavily on mixins. That said, if you've got a website of any complexity then you're using gzip compression for your static assets, and the compressed file sizes are pretty much identical. In terms of rendering performance, I've not seen any comparisons but anecdotally, I've not noticed any slowdown.
- anatoli 18y agoBloat doesn't necessarily mean code size. It could also mean redundant selectors, code that is difficult to maintain, and plethora of other things. As mentioned previously, I'm a front-end web developer, I spend majority of my time coding graphically-heavy designs in CSS and maintaining them, as well as doing JavaScript. In my experience, Sass has been a nightmare. So far, the only people that I've heard praise Sass are back-end programmers, rather than full-on front-end developers.
- chriseppstein 18y agoI doubt you'll ever return to Sass, but I wanted you to know that we did take away that there's not really a good reason to force 1 style per line. We're going to add support for semi-colon delimited styles on the same line. No one has ever complained about it on the mailing list before...
- gommm 18y agoJust wanted to thank you chriseppstein for the all the work you've put into Compass and now into Sass
- chriseppstein 18y agoThanks! It's open source, so, you know, you can put hard work into them too! :-P