Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Sly vs cssnext, the Slant community recommends cssnext for most people. In the question“What are the best CSS preprocessors/postprocessors?” cssnext is ranked 5th while Sly is ranked 8th. The most important reason people chose cssnext is:
cssnext is a PostCSS plugin, which makes it pretty easy to use for people who are already using PostCSS.
Question Ranking
Pros
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.
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 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.
Con Not stable
Sly is in the alpha stage.
Con Lack of support in IDEs
Currently there is very little support for syntax highlighting when writing PostCSS plugins.
