First off, you can compile LESS server-side. Whereas Sass compiles server-side using Rails, LESS does so using Node.js, thus scoring several nerd-core points.
For an even easier way to compile LESS, you can also download the Less app that runs in the background and compiles a
.css file whenever a
.less file is saved in one of the app’s watched folders. To make a folder watched, you simply drag it into the app. Nothing could be easier. So you end up with a css file that you can use locally and for deployment, written in LESS, compiled as CSS, and you don’t have to worry about Node.
I realize that I’m probably coming across sounding like a complete LESS fan-boy. And don’t get me wrong, I do really love working with LESS. But I just felt behooved as someone that uses LESS and doesn’t compile client-side, to counter this common misconception and remind folks about non client-side methods of compiling LESS code.
Update – 7/4/15: I’ve long since moved from LESS to SCSS when it became evident that SCSS was far more actively maintained and had eclipsed LESS in features and community adoption.