Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing PostCSS vs cssnext, the Slant community recommends PostCSS for most people. In the question“What are the best CSS preprocessors/postprocessors?” PostCSS is ranked 4th while cssnext is ranked 5th. The most important reason people chose PostCSS is:
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
Question Ranking
Pros
Pro Fast
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
Pro Flexible
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.
Pro Doesn't force designers to learn a new syntax
Rather than learn a different syntax, PostCSS allows you to write in pure CSS.
Pro JavaScript-based out of the box
Since it's basically CSS extended through JavaScript it works in the browser directly without the need to compile it beforehand.
Pro Built on PostCSS
cssnext is a PostCSS plugin, which makes it pretty easy to use for people who are already using PostCSS.
Pro JavaScript-based
Because the parser/compiler can function in a web browser, it can be used with systems that cannot run similar technology on the server. For example, you could build a WordPress plugin with a front-end application that transforms CSS.
Pro No need to learn a new syntax
Since css-next only adds new CSS features in a way that all browsers can support it, it's still CSS. So there's no need to learn any new syntax.
Cons
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 Outdatet, plugins are often based on different postcss versions and don't work together properly
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 Lack of support in IDEs
Currently there is very little support for syntax highlighting when writing PostCSS plugins.
