4 ms·
I'm just getting into web dev, and the amount of choices is rather overwhelming. I know the basics of html, css, javascript, and ruby. I'm trying to decide wh
by cgag 15y ago
I'm just getting into web dev, and the amount of choices is rather overwhelming. I know the basics of html, css, javascript, and ruby. I'm trying to decide where I should start devoting my time though if I'd like to move into freelancing, but it's hard to decide which way to go with rails, sinatra, padrino, node, express, tower, ember, and so on.
I can see the value in less or sass, but I'd like to see more details on why you recommend one over the other. Same goes for most of the choices.
- karterk 15y agoMy take on pre-processors like LESS, SASS etc. is this: To truly appreciate and benefit from them, you should first start facing problems in scaling and managing plain CSS. I would argue that the same goes for CoffeScript. For simple apps, preprocessors offer negligible value addition.
- delwin 15y agoIf there's a good enough workflow, there's no reason to not use LESS and SASS in each app. You compile the CSS before production anyway, which means you work with beautiful code, and use automatically minified code for production, and all of it is (usually) taken care of in the background. Plus, if I work in CSS for simple apps and LESS for complex apps, I have to keep two sets of boilerplates. I don't want to be writing CSS from scratch every time I make an app. With using LESS in every instance, not only do I only need one boilerplate, but that boilerplate is modular and I can take the things I need and exclude the things I don't. LESS effectively has namespaces to make this super easy and MORE efficient than plain CSS. No comment on CoffeeScript, though. I've not had to write enough JS to warrant checking it out in depth.