Less vs Sass: What are the differences?
What is Less? The dynamic stylesheet language. Less is a CSS pre-processor, meaning that it extends the CSS language, adding features that allow variables, mixins, functions and many other techniques that allow you to make CSS that is more maintainable, themable and extendable.
What is Sass? Syntactically Awesome Style Sheets. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.
Less and Sass can be categorized as "CSS Pre-processors / Extensions" tools.
"Better than css", "Variables" and "Mixins" are the key factors why developers consider Less; whereas "Variables", "Mixins" and "Nested rules" are the primary reasons why Sass is favored.
Less and Sass are both open source tools. It seems that Less with 16K GitHub stars and 3.46K forks on GitHub has more adoption than Sass with 12K GitHub stars and 1.93K GitHub forks.
According to the StackShare community, Sass has a broader approval, being mentioned in 2082 company stacks & 1445 developers stacks; compared to Less, which is listed in 496 company stacks and 168 developer stacks.
What is Less?
What is Sass?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Less?
What are the cons of using Sass?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Absolutely fantastic, not only does it allow for modularity but it is armed with the most useful features like colour operations and nested styles to make you achive more by writing LESS.
It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.
Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.
When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.
Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.
CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.
love me some less. been less styling for around 3 years. makes working with bootstrap and responsive website a breeze. so much power in the language.
Customise the UIkit Front-End Framework, because of that is used to create the application CSS. I prefer SASS but is equivalent.
CSS Preprocessor, used primarily for variables to ensure brand colour continuity.