cssnext VS scss/sasss/stylus. Is it worth it to switch?

Question

css

Friends, I have been using PostCss technology in conjunction with SCSS for some time now. In particular autoprefixer, short, uncss, of course postcss-scss and others. But the question is not so much about PostCss, but about the ability to use CSS 4 today with the help of the postcss-cssnext plugin. Do you think it's worth starting to move from preprocessors to CSS tomorrow?
At first glance, I did not see anything supernatural:
Mathematical operations, working with variables, all this is much more compact in preprocessors.

Some things like custom media are slightly nicer in syntax than similar mixins in scss.
Maybe someone has more experience with this tool, there are some significant advantages?
______________________________
ADDED
An exhaustive article with a detailed analysis of the issue - CSS-Live

Answer 1

Preprocessors are only for the convenience of writing code. They do not provide any advantages for the browser.
And the future CSS4 gives advantages specifically for the browser. For example:
- Significant client-side rendering optimizations are possible;
- a smaller code will be transmitted over the network ...

Answer 2

I totally agree with this guy .

Answer 3

IMHO it's better to stay on Sass/Scss + autoprefixer.
There is nothing revolutionary in PostCSS yet.

Answer 4

This CSS4 pisses me off .
It's just a first step towards making CSS more versatile. The way we see it through the prism of preprocessors. And more steps are needed...
Well, if you are completely satisfied with the capabilities of the four, then what's the problem? Use! And since the support is still lame, cssnext is here to help.
Ps: I don’t even doubt that when CSS4 is brought to mind, SASS -> CSS4 compilers will appear .

Answer 5

Requests for layout in
postcss/sass - 1
sass - 100+