Comment by tracker1 | Hacker News Reader

Comment by tracker1 | Hacker News Reader

Parent Full thread

If you use Bootstrap from the source, it's actually pretty modular. I bring it in with npm, then copy the bootstrap.less and variables.less into my own project (updating the references to those in the node_modules path)... this lets me do quite a bit in terms of not loading the kitchen sink, while still being flexible.

As an aside, I'm not quite sure why less hasn't won over sass... By nature of less being JS driven it is much closer to best in breed tools you need anyway for web development (npm) in my opinion. It kind of bugs me that to do modern web development, you are likely to want/need to have Node (or io.js), Python and Ruby installed. I tend to stick to Node based tools (there is sass for node, but it brings in a binary module). This isn't to be expressly negative, just that I'm surprised there's still broad support for both less and sass... with sass having a bit of an edge in the greater community, it would seem.

If you have docker installed, you can use this 9 MB sass image instead of installing ruby or compiling node-sass: https://registry.hub.docker.com/u/jbergknoff/sass/

Do developers really care whether a tool is written in JS rather than Ruby, or vice-versa? If you're running *nix it's pretty likely you have Ruby installed out of the box anyway.

There's nothing inherently tying you to Ruby anyhow, anyone could write a SASS parser in JavaScript. It's just that nobody has because there is no need for it.

The SASS team are writing one in JavaScript so they must feel there's a need: https://github.com/sass/node-sass

Node-sass isn't a JavaScript port of SASS, it's a Node.JS binding for libsass, the native (C) SASS compiler. The first paragraph of the readme tells you as much.

It's more convenient to be able to handle all dependencies through the same package manager.

Personally I prefer Scala and thus use SBT for most dependencies, requiring the user to use Bundler or NPM as well for just one dependency can get a bit annoying. In the case of SBT it actually does have some integration with NPM since it's used so much for client assets (and there is Trireme which is a pure-Java Node clone), but Ruby dependencies still mean adding one or two manual build steps.

Sass is more powerful

Reply on news.ycombinator.com