19 ms·
There are some reasons for using one or the other depending on your needs. Ruby vs. JS, for one.
by pault 14y ago
There are some reasons for using one or the other depending on your needs. Ruby vs. JS, for one.
- fourstar 14y agoI disagree. I used to use LESS since I could use node, but quickly realized it's inferior to the Sass/Compass combo. 99.9% of the servers that you are able to run node.js on will also allow you to install/run Ruby. What are the other reasons that I'm missing?
- jeremiep 14y agoI'm curious about what makes Sass/Compass superior to LESS?
- grabastic 14y agoA simple example... // Less .rounded-corners (@radius: 5px) { -webkit-border-radius: @radius; -moz-border-radius: @radius; -ms-border-radius: @radius; -o-border-radius: @radius; border-radius: @radius; } // Sass + Compass .rounded-corners { // All vendor prefixes are generated for you @include border-radius(5px); } I'm sure there are plugins for Less that can accomplish the same. I just grabbed this code from the Less homepage. Another thing... Sass has much nicer control flow (if/else, while, for) that can create very powerful mixins.