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:
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
What's about the two language modes .scss and .sass. It feels to me that the former one is far more supported and widely used in contrast to the latter one. What are your thoughts about it and how do you handle current feature releases for both modes?
Are there any projects out there that use Atomic design principles with Sass, webpack, vue/React/any component structure that you'd refer someone to if asked how to implement a maintainable large scale application in a team environment?
Why SCSS? Just to make the Sass syntax easy or was there some other reason behind it?
Will CSS go SASS only? Meaning that browsers will supports SASS?
What CSS naming convention would you suggest for the most optimal use of Sass?
What was the most interesting scssy code refactoring you've ever done in a project? Could be just the concept not the actual code. (although that would be awesome!)
Which is the recommended way to use Sass with React? Should I merge my Sass code with the .js code, or should I put my Sass code apart from the .js code? Do you guys know a tutorial, article or something about this? Hampton, please, show me some light about this, you are using React in Rent the Runway, right?
What inspired you to create the Saas framework?
What future awaits Sass regarding features? Anything new planned to come and make our web dev lives easier?
Sass is so good that I can't stop myself from using nesting feature. What level of nesting is good according to you?
What's your opinion on beginners learning CSS preprocessors without learning CSS properly? Do you think it'll help them?
This is a general question for all three of you! :)
What dev tools do you use daily?
As you mentioned "Sass is only as powerful and CSS allows it to be"..
What are the top 3 CSS features is in your wishlist that Sass can leverage?
How might Sass evolve to support deeper integration with JavaScript-oriented front end toolkits?
Looking back at the history of CSS & Sass, is there a list of new CSS features that you attribute to direct influence from Sass? For example, jQuery is credited with bringing things like document.querySelector() to JavaScript, after years of Sass how has it shaped CSS as a language?
A lot of the newer features people are experimenting with in CSS are client-side only, and can't be compiled, predicted, or rendered in advance. Do you foresee the need (or popularity) of client-side re-processors in addition to preprocessors? What new features could client-side re-processed Sass include that aren't possible to support in its current form as a preprocessor today?
What is the correct term to refer to a developer who uses Sass:
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?
What new features/updates can we look forward to in the future?
I have one at Rent The Runway... but it's not open source. :)
Michael Mifsud
Chris Eppstein
Sass Core Team Member, Engineer @ LinkedIn
Chris Eppstein
Sass Core Team Member, Engineer @ LinkedIn
James Gallagher
I am the CEO of an Application Hosting Company - https://myrskyt.com
Name one word to describe your framework.