O
O
OnYourLips2014-12-20 08:21:52
css
OnYourLips, 2014-12-20 08:21:52

Less vs Sass: which is more promising?

The outlook is short term.
Tried googling and came to the conclusion that they are pretty much the same and both are much better than pure CSS.
In the direction of Sass, they say that Compass is its plus, but it has many analogues for both preprocessors. Even IDEs can track and compile them on the fly.
Not to mention build tools that support both preprocessors.
Do any of them have any advantage?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
A
Alexander Goncharov, 2014-12-20
@websanya

Sass has one undeniable advantage - the community. There are many more different mixins written for it and most of them can even be used. Besides Compass and Bourbon, two big frameworks, there is also Susy. And this is also a huge plus for the Sass preprocessor.
Susy is a grid management system based not on static presentation classes, but on a flexible mathematical system that is very easy to customize.
We have a lot of videos about Sass on the channel, take a look and decide whether it suits you or not:
- Sass basics ,
- working with constructions in Sass (branching, loops) ,
- Compass basics ,
- creating a vertical rhythm with Compass ,
- work with Susy
- and much more!

R
Rikcon, 2014-12-20
@Rikcon

+ Less is that valid css = valid less.
But with sAss, this will not work. Only with sCss.

I
Ivan, 2014-12-22
@Fransic

Try compass I now only use compass

N
Nikolai Antonov, 2015-04-21
@my-nickname

I used sass(scss) for a long time, but recently I had to use less, and to be honest, I like less better, it compiles faster, there is no "@" - "." instead of them, more understandable and beautiful. When there are a lot of files, the speed of work is very noticeable.
If you decide to use sass, I want to add more - compass is evil, it's better to use libsass.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question