4 ms·
ok didn't know about the platform support. i'm curious what use cases have you run into where the less.js produced different css then lessc?
by c4urself 15y ago
ok didn't know about the platform support.
i'm curious what use cases have you run into where the less.js produced different css then lessc?
- upthedale 15y agoI haven't used Less, although I have been considering it recently. My point was much more general though. A tool like this seems great to help catch problems early - earlier than your deployment step. Can you be absolutely sure that there aren't any latent bugs in Less or differences between lessc and less.js, such that you could never have any differences between your less.js-backed dev code and your lessc-backed deployed code? Even if the codepaths are identical between lessc and less.js, their execution environments aren't. All I'm saying is that if you're going to use some _thing_ in your deployment scenarios, it would make sense to use the exact same thing throughout your development (where possible). The biggest argument against this in the case of Less is the hassle of compiling it. That's where a tool like SimpLESS or less.app steps up.
- Ysx 15y agolessc is part of less.js (https://github.com/cloudhead/less.js/blob/master/bin/lessc https://github.com/cloudhead/less.js/blob/master/bin/lessc), so should be identical, but fair point.