I’m so suspicious about LESS for css. But I hear only good things about it. It can’t be that bad, right?
My biggest concerns is that you compile something suspiciously like CSS into CSS. Can you gain anything at all in doing that? In almost all of the examples, you end up with less CSS, than you have LESS. Take the bootstrap.less for example, the framework from twitter, where 105kb of less ends up with 94kbs of css. Isn’t the point of the mix-ins and operations that you can re-use your code. Shouldn’t a few lines of LESS produce MORE CSS? It just seems inefficient to me.
But I can accept that file-size is not the point. My HOPE is that the point of LESS is that it makes things easier to maintain.
—
I tried to compile the bootstrap.less into css using WinLESS, which crashed, pretty violently, some kind of null error (I use a Japanese programming environment, so all error messages doesn’t make sense to me, but it seemed pretty bad.) Then I tried with SimpLESS, which failed almost as hard, but at least pointed out a error in my bootstrap.less. (So much for GUI’s).
Then I tried looking for plug-ins for my favorite texteditor (Sublime Text), and found https://github.com/berfarah/LESS-build-sublime. Which also failed compiling. But after updating a dependency (http://www.dotlesscss.org/) manually and editing the sublime-build files to get the correct path to my project (I hardcoded the path, so god may have killed a kitten on my behalf today), finally the less-file complied. And I ended up with a beautiful css file with only 4000 lines.
My projects has always been on a smaller scale. So I have a hard time seeing how one could possibly end up with even 1k lines . And I get chills down my spine if I get near 500 lines of css. Maybe less is just overkill for projects of my size. Or maybe that’s just bootstrap. I still plan to learn it properly. But that is good enough for one day.