Hi and thanks for this article,

Today SASS brings a modular approach of CSS in a classic project. The management of import with @use, @forward and the use of namespaces and private variables make it a competitor to the Full React project or equivalent.

Depending on your project the use of SASS has a real interest as the use of TypeScript vs Javascript, but that's another story.

When I was learning the front-end, a wise woman said that I need a solid understanding of HTML, CSS, and JavaScript.

I kept hearing more and more: Frameworks and Library's come and go. I experienced that first hand when moving from Bootstrap 2 to 3, and from 3 to 4. The point is that I was learning a library/framework and not understanding CSS.

I read an article by Cathy Dutton: Stepping away from Sass

I started focusing on CSS more.

I use it because it makes responsive design much easier, especially because it allows you to nest media queries.

Although I don't use Sass everyday I think it's great and you had many valid points. Sass makes a developer's life easier :)

Sass is still a great tool, another reason I keep using it is scalability and organization. Being able to leave alone the compiled main CSS file and break layouts, components, variables, etc. Into multiple files in an easy to manage file structure makes my life more easier.

Thank you