Need advice about which tool to choose?Ask the StackShare community!
Compass vs Sass: What are the differences?
What is Compass? A Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain. The compass core framework is a design-agnostic framework that provides common code that would otherwise be duplicated across other frameworks and extensions.
What is Sass? Syntactically Awesome Style Sheets. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.
Compass and Sass can be categorized as "CSS Pre-processors / Extensions" tools.
"No vendor prefix CSS pain" is the primary reason why developers consider Compass over the competitors, whereas "Variables" was stated as the key factor in picking Sass.
Compass and Sass are both open source tools. Sass with 12K GitHub stars and 1.93K forks on GitHub appears to be more popular than Compass with 6.91K GitHub stars and 1.23K GitHub forks.
Airbnb, Square, and Pandora are some of the popular companies that use Sass, whereas Compass is used by Weebly, Movielala, and Custora. Sass has a broader approval, being mentioned in 2098 company stacks & 1484 developers stacks; compared to Compass, which is listed in 88 company stacks and 42 developer stacks.
Originally, I was going to start using Sass with Parcel, but then I learned about Stylus, which looked interesting because it can get the property values of something directly instead of through variables, and PostCSS, which looked interesting because you can customize your Pre/Post-processing. Which tool would you recommend?
We extensively use Sass
and CSS Modules
as our styling solution at Vinted. Even though we considered adopting a CSS-in-JS library, we ultimately leaned towards the flexibility that Sass and CSS Modules offer.
Vinted also has an internal design system where Storybook
is used for development and documentation.
We know that Sass
is not a replace for CSS
, but in my mind there is no CSS with no Sass.
One of the first complement/plugins I add to the environment, are the Sass processing files/demons.
I couldn't imagine going back to pure CSS. Sass is even the way to go, regarding Styled Components, CSS Modules, and all the other options.
JSS is makes a lot of sense when styling React components and styled-components is a really nice implementation of JSS. I still get to write pure CSS, but in a more componentized way. With CSS post-processors like SASS and LESS, you spend a lot of time deciding where your .scss or .less files belong, which classes should be shared, and generally fighting the component nature of React. With styled-components, you get the best of CSS and React. In this project, I have ZERO CSS files or global CSS classes and I leverage mixins quite a bit.
Pros of Compass
- No vendor prefix CSS pain9
- Mixins1
- Variables1
- Compass sprites1
Pros of Sass
- Variables613
- Mixins594
- Nested rules466
- Maintainable410
- Functions300
- Modular flexible code149
- Open source143
- Selector inheritance112
- Dynamic107
- Better than cs96
- Used by Bootstrap5
- If and for function3
- Better than less2
- Inheritance (@extend)1
- Custom functions1
Sign up to add or upvote prosMake informed product decisions
Cons of Compass
Cons of Sass
- Needs to be compiled6