Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Is Sass worth it ?

I've been checking out the videos on Sass and although it seems like a nice thing. It seems a bit too much when creating websites that might not be very complex. I think Sass is maybe better in big projects or large projects i just wanted to know some of your opinions on the matter.

5 Answers

Josh Page
Josh Page
1,928 Points

I agree that Sass is best for big projects or for beginners who don't want to learn complex level css. Most of Sass's features which you would use on small projects such as nesting and inheritance can be easily accomplished using just CSS if you have the knowledge. But if you are producing large scale websites Sass is very useful as the variables and include functions allow you the edit many CSS files and elements easily, potentially saving you a lot of time by giving you access to a function much like php include but in CSS. I would say, if you are only working on small projects, it is much better to get a advanced level knowledge of CSS before you begin learning Sass.

I would too be interested in hearing anyone else's opinions though?


Seems a bit extreme unless your building complex sites like treehouse

Pablo Diaz
Pablo Diaz
2,849 Points

I got into sass a couple of months ago. I cannot begin to tell you the difference it makes not only in big but also in small projects.

Kevin Korte
Kevin Korte
28,148 Points

I use Sass on every project. It's an indispensable tool for me now. Many times, I might not use a lot of the features like extending. I have a few default mixins i like, like a clearfix mixin I can resuse project to project.

I also have an em mixin so I can declare my Sass in pixel values, but the actually compiled code is in EM's.

I also have a REM function that allows me to input a pixel value, and but it outputs a REM value with a pixel fallback automatically. Big or small, these are awesome tools.

I absolutely love setting colors to variables. I do that for every project. Than I tend to use the lighten or darken color function of Sass for borders and highlights. The nice part is if I build that way, and ever decide to change the color, I change it in one spot and everything updates, even the borders and highlights thanks to those functions.

I always use the nesting feature, I love that. I love being able to nest a &:hover to write my hover pseudo classes. It really speeds up the work flow not having to write out that selector time and time again for every pseudo class.

I really enjoy it. I think any project can benefit from it. I've been using Prepos lately to very quickly get to compiling Sass. I've also used Grunt, but for small sites I'm not sure it's worth the time to set up.

It's awesome to hear different opinions i think i will try to incorporate this into my workflow after too reading more articles it seems like a really quick way to write css in a single line

There's an excerpt from Dan Cederholm's book on Sass over at A List Apart. If you ever decide to delve in yourself you might check out LibSass and possibly CodeKit.

I think one of Dan's points was how much easier Sass can make CSS. Some might disagree but it's possible things like Sass and other web design tools will be doing a lot of the brain and manual work in the future.

I think it's getting used to writing css and knowing when to switch between Sass that i might just need to get used too sounds weird but oh well.