Here’s the Deal

CSS-Crush vs Sly

2 1

When comparing CSS-Crush vs Sly, the Slant community recommends Sly for most people. In the question“What are the best CSS preprocessors/postprocessors?” Sly is ranked 8th while CSS-Crush is ranked 14th. The most important reason people chose Sly is:

By using whitespaces and nesting, you don't need braces or semicolons. This helps with keeping the syntax as readable and minimal as possible.

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best CSS preprocessors/postprocessors?

CSS-Crush

Sly

Pros

Pro
Out of the box vendor prefixing

Rather than require a plugin, CSS-Crush will automatically add vendor prefixes.

Pro
Implemented in PHP

PHP is used in common platforms such as Drupal and Wordpress, which results in CSS-Crush being easy to integrate with most development stacks.

Pro
Readable syntax

By using whitespaces and nesting, you don't need braces or semicolons. This helps with keeping the syntax as readable and minimal as possible.

Pro
Supports variables out of the box

Sly has out of the box support for variables.

Ad
Cons

Con
Not widely used

CSS-Crush is not a widely used option. The small community of users results in a harder time finding answers to any questions you may have.

Con
Extremely limited adoption

Sly has just 5 stars on Github and a very small adoption rate. For an open source project this usually means less bugs reported, lesser documentation and few third-party learning resources.