Sass vs. PostCSS

All CSS written in Sass

Makes our CSS very maintainable by allowing for easily creating logical folder structures, variables and reusable mixins.

To make my CSS more efficient, better, and most importantly more fun!

lala

Definitely nice to be able to nest your styling and not have to have separate blocks of CSS. We’re using a lot of media queries to make the site responsive.

I use sass only to @import my components to have a better readability than all stuff put in one page of css

Jekyll uses Sass. I like to use Sass. This stack now uses Sass.

faster, smarter CSS

All of our CSS is written in SCSS, Sass's CSS-like syntax. Variables, functions, mixins, and nesting are simply heaven compared to plain CSS.

You still write CSS without??

SASS is better than CSS. You can read what is going on.

Sass is what CSS should have been. We use Sass to keep our stylesheets organized and to reduce duplication, making changes way easier.

Website front end styling

5 years of experience using Sass for CSS development and compilation.

Pre-processing CSS

We write all of our styles in SASS and compile them using Grunt.

I won't write pure css anymore, after getting to know this nice preprocessor.

Sass is being used to keep our stylesheets organized in addition to the typical use cases (variables, mixins, functions, etc).

CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.

Clean superset of css and integrates easily with other packages being used.

Css preprocessor

DRY. The core concept of Ruby, and the more I learn Ruby on Rails, the more I realize the importance of something like sass.

We use Sass to create CSS wherever we can

Client UI

To compile the front-end SCSS files into the styles.css file.

Pre-processor for frontend App

only used this because people hated less, back then you still could not import('something.css') as scss ...

전 css보단 sass가 좋습니다.

반복하여 작성해야하는 css 코드를 sass 코드 몇줄로 줄일수 있고 분기처리, 함수 사용도 되는 강점이 강력한 생산성이 됨을 경험하였습니다.

My go-to way to write CSS, especially since it includes variables

Pre-processed CSS

All of our CSS is first written in Sass (SCSS specifically). It is much easier to read and can keep styles DRYer with variables and functions.

basic

All of our scss is compiled with sass-rails.

It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.

Only limited usage for css management

All of our custom CSS is extended with sass before deployment.

Use of mixins and variables for styling makes work easier

Build CSS

Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.

Sass is a CSS preprocessor that adds nice functionality such as nested styles, imports, mixins, variables etc.

Speed up CSS development, and separate code into logical files.

Compiling Bootstrap customization.

Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.

Advanced CSS styling

To compile CSS in conjunction with Compass and Grunt

When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.

We use SASS to make our CSS easier to read as well as making updates to colour schemes or global margins quicker and easier than having to modify individual files.

It's elegant, nested css!!! Great mixins, variables, etc.

Oh I fell in love when tried SASS the first time, modularizing and functions for all things... well not all but the most repeating ones.

We prefer stylus over saas. We are not using saas.

CSSNext, import, loaders, nesting. Components written using BEM style.

PostCSS handles compiling node-based CSS libraries, including BassCSS (the whole site is only ~85 lines of custom CSS). It also does auto-vendor-prefixing and support for CSS variables.

Compiles future CSS.

We wrote a lot of flexbox and css that needed prefixing. PostCSS + Webpack was the best option here.

autoprefixer to support multiple browsers automatically (with webpack plugin)

We use PostCSS to improve cross-browser compatibility

PostCSS essentially allows you to set up your own CSS preprocessor with the features that matter to you. It has a modular plugin-based architecture, which means that if someone comes up with a useful new feature, you can easily add it to your stack as a PostCSS plugin. PreCSS and PostCSS-cssnext are some of my go-to plugins.

Used to minify and extend the CSS markup of the framework.