LESS css - JS Parser vs Compiled
css, less
Solution
Its not slow on fast computers/browsers. However depending on your target audience I wouldn't use it.
I would rather setup `lessc` to watch a file/directory and generate css files on save. And then commit both the less and the css files to your SCM (that is infact what I do).
Also doing it this way allows for continuous integration builds.
http://en.wikipedia.org/wiki/Continuous_integration
Problem
I was wondering if anyone knew if the JS interpreter for LESS css causes any noticeable delays in page loading. I would prefer to use the JS parser simply because it's easier to use, since I won't have to run the compiler after every edit and easier to manage the source code as SCM tools won't be tracking both the .less and .css files