sass

CSS has come a long way in recent years, and some of the benefits that Sass and other preprocessors offer us, which have been so popular with developers, are already incorporated into the language.

So how relevant is Sass to current development? Is it worth using it? Is it worth the time to learn it? The answer depends a lot on who you’re asking the question, because there are just as many reasons to continue adopting Sass as there are reasons not to.

Sass Apprenticeship

Learning Sass is not difficult. With what you know about CSS and a little more, you are able to use its advantages. For this reason, the investment of learning to use the tool is undoubtedly small for the benefits that it continues to bring us.

Features supported by CSS

Although CSS variables are already fully supported, as well as simple calculations using calc, Sass continues to provide various interesting extras, such as style nesting (it’s also coming to CSS), mixins, or the ability to concatenate multiple style sheets in a single file. single file.

This means that although CSS has improved, Sass still makes sense today. Over time this landscape may change, but standards always go slowly, whereas Sass already delivers.

Tools Similar To Sass

Currently some tools in the frontend ecosystem such as have gained enough strength and manage to provide similar benefits, and some more that are not included in Sass.

However, the truth is that among the most common CSS tools used by developers, Sass is the undisputed leader, both in terms of users and in terms of their satisfaction.

Development flow with Sass increases your requirements

The only downside we could objectively pin on Sass is that it adds build complexity for us. It is undeniable that it means an additional step to the frontend development flows.

However, it is also worth mentioning that most modern frontend projects require compilation of different assets, such as Javascript or optimization of files such as images or SVG. This is why, although Sass requires us to compile the code to produce the standard CSS, the fact is that we are already needing to compile other pieces of software, so this disadvantage is greatly mitigated.

Developer satisfaction

In conclusion, it is true that we can find reasons not to use Sass, but they all have counterparts that offer us arguments in favor. In objective terms, Sass is still an extremely used toolas evidenced by satisfaction surveys of frontend developers.

In 2022 the technology continues to be supported. In fact, Sass year after year is among the most satisfied and most used CSS tools within the CSS landscape. For this reason we can say that it is worth continuing to trust Sass.