Design comparison
Solution retrospective
This is my first project where I used Sass. I found Sass slightly repellent and unnecessary (e.g. file/code duplication) but finally decided to give it a try. While my impressions are positive I still believe that we should give priority to plain CSS. Why should we use Sass? What are your thoughts about it?
Community feedback
- @md5daltonPosted about 2 years ago
Greetings Željko 👋
I'll jump straight to the point of why you should use SASS. Syntactically Awesome Style Sheets - is a CSS preprocessor and it was developed to solve the problem of excessive repetition in CSS by allowing for variables, nesting, and mixins. Programmatic features such as arguments, loops, and conditional logic were added. The SASS syntax eliminates the need for semicolons and curly braces. Another newer syntax is SCSS (Sassy CSS), and is simply CSS with the same featureset as SASS but requires semicolons and curly braces just like CSS.
You can choose whichever syntax you wish to, since both have pros and cons. I've been using the SASS syntax because there's no need for semicolons and curly braces. The CSS preprocessor itself is great, one other thing I really loved about it was SASS partials, which allow developers to split the styles and compile them into one file later. It has saved me a lot of time and headaches in maintaining huge styles as the project increases in size.
And not to forget SASS is the most popular CSS preprocessor so there are plenty of resources to learn from👌
1
Please log in to post a comment
Log in with GitHub
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord