Is anyone really using SASS anymore?

I've been using Tailwind along with PostCSS and it's made me really love not using SASS.

• I don't think sass will lose it relevance any time soon. Even in today's landscape. Recent css features are cool but using them is cumbersome compared to what sass have. And compiling scss to generate so called CSS4 file is best of both world. Take a read on this article codepen.io/jakealbaugh/post/css4-v.... This article and its update demonstrate how we can utilize best of modern css features while still having coding convenience of scss.

• I am still using scss because I hate using large css framework. Using scss gives me benefit of having a semi-actual programming language to create optimised css for the site. I was also inspired by 2014 talk from Heydon Pickering for a clean and minimal css approach.

• I have used tailwind with sass for quick prototyping. But for production, I would still keep sass ui project.

• My tip is to watch "heydon pickering | effortless style 2014". It will change the way you approach styling. Also Blogs on codepen are great resource. My fav author is Jake Albaugh and Chris Coyier

I am using SCSS. I would avoid indented syntaxes, as in SASS, if possible. Also SCSS is more similar to CSS.

SCSS allows me to use nested CSS and CSS variables. Well, I am not sure about caniuse.com/#feat=css-variables

There is also LESS and Stylus.

IMO, you should use at least post-CSS, to ensure compatibility.

For wholly web browser environment (no Node, no OS), I like stylis.js.

I prefer CSS Variables. I learned LESS and hadn't tried SASS. To each their own.

When I was learning front-end, many tutorials had some CSS but mostly Bootstrap 3, or Bulma, or Materialize-CSS, etc. It got confusing and limited my understanding of CSS.

I once read: "Frameworks come and go. If you want to do front-end, you need to have a solid understanding of HTML, CSS, and JavaScript." I think that was from the Odin Project?

I still go over tutorials and if they used SASS, I just use CSS Variables.

• I don't think it will lose its relevance any time soon.

• I am loving Sass(SCSS) more than ever. Namespacing is really helpful when working with it. It has also helped 'error'-ing when compiling so that I won't miss some typos.

• None. I haven't any reason to move yet. If there's a chance, maybe.

I hate SASS.
I hate libs using SASS.
Can you move on already?
Can you make it any harder for anyone else to use your code?
Why do you need to compile styles in 2020?
Why does the compiler not work with my OS and Node version from first try in 95% of times?

Of course.
I like writing style systems instead of using the atomic css approach of Tailwind and co.
Sass (or scss in my case) helps me with three major points

• Nesting. I write my styles in between BEM and SMACSS. Nesting helps me with namespacing.
• Mixins. Those are awesome for helper classes that you may or may not need. Mixins don't get rendered by default if the stylesheet doesn't require it. It allows me to tree shake a library of helpers. I used to use sass-variables for everything too, but phased that out in favor for custom properties.
• component structure. Helps me stay sane, when every component has its own file. But bundling everything up is necessary to improve the network waterfall. That's something CSS-imports can't do.

I think sass is losing relevance, but for the wrong reasons. Native css is growing and the working group is discussing things like native nesting. That would be my main reason to abandon sass for just native css.
However it's mostly losing relevance because of Utility-first frameworks. I don't believe those are the answer to complex style systems, since they're aiming to reduce relationships between elements to zero. Those can be very powerful, if wielded with care.

I think that Sass will remain relevant as long as there are major frameworks that use it. The move that Bootstrap did from Less to Sass practically buried the first one and gave a big boost to the second one.

I am using both Less and Sass because many client projects run on legacy codebases and were developed during a time when Less was more mainstream (again, due to Bootstrap). I never got to the point where I was a power user, but currently, I find it less convenient to write only vanilla CSS.

Variables in CSS are starting to make Sass and similar preprocessors less necessary, but the nesting is invaluable in my view, so I don’t think it should be deemed a dead technology.

In React I use Styled Components because I love making single-file components, but I’d use Sass if I were making single-file components in Vue or if I were using some other frameworks.

What I’m currently interested in is how we can share styling across native mobile apps and web apps. Styled Components seems like it could help with that, but I haven’t seen anything that would make Sass viable for that, so that’s where it may fall down.

I really really hate SASS! This is because SASS simply erased months of my life!
At this point you may think: oh, poor guy, coding is not for everyone, but don't get me wrong: I have bult a very complex frontend framework... using SASS. I didn't know about tailwind at that time, and when I learned about it... it was too late to change all my code base . So, my advice for anyone trying to decide what to use is: do not use SASS!
When someone starts a project to learn web developement it may think SASS is a beautifull way to combine classes, to nest some rules, and so on... But as the project gows the problems starts to arrise! Some of the problems are:

• file referencing system, SASS finally realized their @import problem and now they switch to @use encouraging ppl to convert their old code into it... but guess what: most of the time is impossible!
• insane amount of bugs, so many that they splitted the libs into multiple variatons to get rid of their old history, but even the new variations contains huge amout of bugs
• arbitrarry author code changes, eg. if some css rules doesn't match their browser compatibility policy they simply just replace it with what they think is good. Please read the mind bending SASS issue469, where they banned me for my opinnions! :))) I bet not many SASS users know that their code is actually changed in the output!
• data types. It would probably take thousands of lines to write about illogical sass data types which in fact are all.. strings. And this is because SASS itself is just a text proccessor, not a language as they claim! The SASS creators should have at least known that one language is not written in another language!

So, what choice do we have to avoid SASS? Well, tailwind is a solution, but in principle the problem can be concluded at the execution of preprocessing in javascript. Using nodejs file referencing system we can load any css file into javascript as text, then we can proccess that text using javascript functions and finally output the result into css files. We really don't need any of SASS "intelligence"...

I think if we can reduce another tool to simply the dev process we should. personally I'm always on the watch for reducing my toolchain...I would say today's css native features get the job done perfectly, I see no reason adding more complications to the dev process.

I am still using it, combined with css module. It's amazing.

Scss for the win! I use it all the time. Sass on the other hand....meh.

You may as well ask if people still use for loops anymore. Are you kidding me? I made an account just to comment on this. YES it is still useful.