It's time to ditch Medium for good! 🌈⚡️

Introducing Devblog by Hashnode. Blog on your domain for FREE. Highly customizable and optimized for developers.

Learn more

Ask anything to Sass Team

CSS on its own can be fun, but stylesheets are getting larger, more complex, and harder to maintain. This is where a preprocessor can help. Sass lets you use features that don't exist in CSS yet like variables, nesting, mixins, inheritance and other nifty goodies that make writing CSS fun again.

Ask Sass Team about:

  • Sass Roadmap
  • Using Sass in your projects
  • LibSass
  • Writing better CSS

Hosted by:

Looks like we answered all the questions on here!

If you have other questions, we aren't a hidden team! We're all over that new Twitter-thing. Thanks for tuning in to our AMA and hopefully we provided some laughs, some tears, and maybe... just maybe... a little love.

/queue Dionne Warwick

Ask a Question

99 discussions

Do you see CSS4 as the end of CSS preprocessors?

Show all replies

If you look at the progression of the CSS specs, they honestly aren't focusing on increasing the complexity of the language and it's syntax. What they are instead focused on is what you can do with the selectors and properties you have. Think, Flexbox and all the lovely features we've been getting.

Further, there are things that just don't make sense for the browser to ever implement.... Sass (and other processors) do a lot of bundling, merging, splitting, importing, etc. Things that just simply make sense on the server side.

No matter how powerful the low-level OS language Assembly gets, your probably going to prefer to use a language one step up, so you can compile and optimize and handle all sorts of nice things we get from higher-level languages. CSS is the core of what's possible, and Sass is trying to make it powerful and easy from a coders perspective.

Reply to this…

Share your programming knowledge and learn from the best developers on Hashnode

Get started

Are there any major benefits of using Sass over Less ?

A better question is there any benefit of using Less over Sass. As I see it, there's very little. The main reason used to be in-browser implementation, but the upcoming release of Dart Sass will enable that. I honestly don't see any reason to use Less anymore, unless you like the syntax better but it's purely an aesthetic choice at this point. Sass has a bigger community, more robust implementations, and is faster with libSass.

Reply to this…

What's your opinion on Styled Components and "CSS in JS" techniques in general?

Show all replies

Yeah, before this AMA, I was coding in my StoreSelector.scss file in a React app. I love styling components individually. Especially I like organizing my SCSS with my JS into Atomic Design elements. :)

Honestly, I challenged myself to use plain CSS in that build platform, and it just started to get really freaking annoying to do BEM. Not having nesting and some basics was :thumbsdown:

Reply to this…

What advices would you give to developers learning Sass for the first time?

Show all replies

There are a lot of great resources out there for getting started with Sass like

My suggestion is to not over use Sass. Instead focus on writing good CSS and incrementally adopt Sass features a bit at a time as they make your life easier.

Reply to this…

With native variables coming in, a nesting spec in candidate recommendation and other interesting features pouring into CSS, Do you think there will be a time when Sass will no longer be needed?

Show all replies

I don't know... maybe!

But, not everything is appropriate to do in the browser. I'd be surprised if we ran out of language-and-syntax improvements that wouldn't be worth the compile time while devving.

Reply to this…

Load more responses