When comparing PostCSS vs CSS-Crush, the Slant community recommends PostCSS for most people. In the question“What are the best CSS preprocessors/postprocessors?” PostCSS is ranked 4th while CSS-Crush is ranked 11th. The most important reason people chose PostCSS is:
PostCSS allows you to opt-in to the features you need with plugins. This allows you to set it up to behave exactly like Sass, with nesting, mixing, extends, and more. On the other hand, it allows you to use plugins by themselves for things like auto-prefixing, minification, and more. You can even set up your own custom "stack" of plugins to do exactly what you like.
Ranked in these QuestionsQuestion Ranking
Pro Doesn't force designers to learn a new syntax
Rather than learn a different syntax, PostCSS allows you to write in pure CSS.
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
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.
Con Harder to install and keep working
The immense flexibility of PostCSS plus its current rapid evolution makes it harder to install, configure and keep running than the more monolithic and mature preprocessors.
Con Some plugins need to run in a certain order
Some plugins can only work if initialized after some other plugins. For example, transforming and applying CSS variables needs to run before running a plugin which uses these variables inside conditional transformations.
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.