Thank you for your comment. As you correctly observed, at first sight, Sass and Less have almost identical functionality. For example, they both can be used for compiling SCSS to CSS. However, the difference between them is bigger than you think. There are cases when Sass is a clear winner. For example, Sass has more robust libraries. Chris Coyer agrees with this point of view, saying in his article that “the language of LESS itself doesn't make it possible to build as robust of libraries on top of it”. Besides, in terms of language ability, Sass is definitely better than its counterpart. It has actual logical and looping operators in the language that is unavailable in Less.
I hope my comment answers your question.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi there!
Thank you for your comment. As you correctly observed, at first sight, Sass and Less have almost identical functionality. For example, they both can be used for compiling SCSS to CSS. However, the difference between them is bigger than you think. There are cases when Sass is a clear winner. For example, Sass has more robust libraries. Chris Coyer agrees with this point of view, saying in his article that “the language of LESS itself doesn't make it possible to build as robust of libraries on top of it”. Besides, in terms of language ability, Sass is definitely better than its counterpart. It has actual logical and looping operators in the language that is unavailable in Less.
I hope my comment answers your question.