In Less, there are also some mixin libraries battling to be the best. There will be some back and forth on which of these project is “ahead.” In Sass, you can use Compass, and Compass will keep itself updated, and thus the prefix situation is handled for you. But you know how you don’t go back and update the prefixes you use on all your projects? (You don’t.) You also won’t update your handcrafted mixins file.
With either language, you can write your own mixins to help with vendor prefixes. The fact that Sass is in Ruby and Less is in JavaScript is of little consequence to most potential users. Maybe you should, but you don’t have to, so it’s not a factor here.
You need to know jack squat about Ruby or the command line or whatever else. You should use an app like CodeKit, LiveReload, or Mixture to watch and compile your authored files. The Much Longer Answer The Learning Curve with Ruby and Command Line and Whatever Slightly longer answer: Sass is better on a whole bunch of different fronts, but if you are already happy in Less, that’s cool, at least you are doing yourself a favor by preprocessing. It’s nice that the conversation has largely turned from whether or not preprocessing is a good idea to which one language is best. I’ve been asked in person several times and an online debate has been popping up every few days it seems. “Which CSS preprocessor language should I choose?” is a hot topic lately.
0 kommentar(er)
