What are the best CSS preprocessors?

[edit][2comments]

Why do you recommend Sass?

Why do you not recommend Sass?

Sass is the default preprocessor for Ruby stylesheets and is probably the second most popular option behind LESS. Sass has a great balance between ha...

Powerful features provide variables logic and functions

[edit][2comments]
Sass has the following key features:Control Directives - Sass control directives provide flow and logic and give you a finite level of decision maki...

Compass framework

[edit][2comments]
Sass can be used with an awesome framework called Compass, which provides the following handy features:It extends Sass with popular css frameworksIt...

Has to be compiled from Ruby

[edit][comments]

[edit][4comments]

Why do you recommend Less?

Why do you not recommend Less?

Less is a great choice if you want the majority of the benefits of a CSS preprocessor without having to learn a new syntax and advanced features.Less...

Easiest preprocessor to learn

[edit][comments]
Because Less has a lightweight feature set, is syntactically similar to CSS and can be run client side with file conversion on a page reload, it is...

Familiar CSS style syntax

[edit][comments]
The LESS syntax is essentially the same as CSS with extensions for dynamic behavior such as variables, mixins, operations and functions.Variables:@co...

Light on features

[edit][comments]

[edit][7comments]

Why do you recommend Stylus?

Why do you not recommend Stylus?

Compared to its competition, Stylus has a superior feature set and an optional, incredibly terse syntax.

Clean, flexible syntax

[edit][2comments]
Stylus has an extremely terse syntax. Colons, semicons and braces are all optional allowing you to write Stylus code however you want. hover-darken(...

The most powerful feature set

[edit][2comments]
Not only does Sylus support all the features from Less and Sass it provides features not found anywhere else:You can get properties from parents and...

No cons added yet

[edit][comments]

Why do you recommend Myth?

Why do you not recommend Myth?

Allows writing future-ready CSS syntax

[edit][comments]

Automatically sets appropriate prefixes

[edit][comments]

Lacks mixins

[edit][comments]

[edit][comments]

Why do you recommend CSS-Crush?

Why do you not recommend CSS-Crush?

No pros added yet

No cons added yet

[edit][comments]

Why do you recommend CSS-On-Diet?

Why do you not recommend CSS-On-Diet?

Easy and fast CSS preprocessor

Easy to learn and use

[edit][comments]
Doesn't require programming skill to work with variables, mixins, media breakpoints

Fast to read and write CSS

[edit][comments]
Works like Emmet, shorting CSS keywords, but it's not limited only to writing. Also modifying and reading COD(CSS-On-Diet) files is faster.

No cons added yet

[edit][comments]

Why do you recommend Rework?

Why do you not recommend Rework?

Rework is a CSS preprocessor that's designed to extend the functionality of vanilla CSS.

Extend native properties

[edit][comments]
Through transforms you can modify existing properties to give them new attributes and options, so instead of managing messy mixins, you can add a sim...

Can work with other preprocessors

[edit][comments]
Although you don't have to, since Rework works on vanilla CSS, you could use another preprocessor that has a syntax you enjoy more before applyi...

No cons added yet

Are we missing something?

Help make this question more complete.