7 ms·

No, I don't mean minify--I mean the SASS has to be run through a preprocessor before you have usable CSS. If I write the CSS, I instantly have usable CSS. I lik

by jsiarto 14y ago

No, I don't mean minify--I mean the SASS has to be run through a preprocessor before you have usable CSS. If I write the CSS, I instantly have usable CSS. I like using minimal tools for web design--browser and text editor. I don't want things I have to compile before I can see them in the browser. I also think the mixins and nesting are overstated in terms of increasing the efficiency of designing sites with CSS. I am not typically declaring colors 20 times, or doing nesting so deep that it becomes confusing. The benefits don't outweigh downsides of dealing with SASS files and preprocessors.

yb66 14y ago
May I enquire, have you used one? Your comments, and those within the article, suggest that you haven't and the writer of the article hasn't. I run the Sass binary, it watches my files, when I save something it runs them through the preprocessor, sees if there are changes and then outputs CSS to a destination I specified (the public folder of the application, obviously). This takes less than a second, so by the time I've switched to the browser and pressed refresh and it's there, styling a web page. I write in SCSS, which is a superset of CSS, so I can actually write the Sass file in CSS, have it preprocessed and minified automatically. In other words, I put in one command to start the SASS binary running, and that's all the extra work right there. So you see, when people talk about extra work, compilation time, waiting around for things etc, they sound like they don't know what they're talking about. Then if you take into account the time saved from all the functions you now have access to, the stuff that will work the same across several browsers, the grids, the sprite stuff, the typography helpers... (the list goes on and on) it can only save you time. I hire designers for jobs and after the mess the last one made through only knowing CSS I've decided I won't hire one who doesn't know SASS. It wastes my time and everyone else's on projects now.

by jsiarto 14y ago

yb66 14y ago

May I enquire, have you used one? Your comments, and those within the article, suggest that you haven't and the writer of the article hasn't. I run the Sass binary, it watches my files, when I save something it runs them through the preprocessor, sees if there are changes and then outputs CSS to a destination I specified (the public folder of the application, obviously). This takes less than a second, so by the time I've switched to the browser and pressed refresh and it's there, styling a web page. I write in SCSS, which is a superset of CSS, so I can actually write the Sass file in CSS, have it preprocessed and minified automatically. In other words, I put in one command to start the SASS binary running, and that's all the extra work right there. So you see, when people talk about extra work, compilation time, waiting around for things etc, they sound like they don't know what they're talking about. Then if you take into account the time saved from all the functions you now have access to, the stuff that will work the same across several browsers, the grids, the sprite stuff, the typography helpers... (the list goes on and on) it can only save you time. I hire designers for jobs and after the mess the last one made through only knowing CSS I've decided I won't hire one who doesn't know SASS. It wastes my time and everyone else's on projects now.