I totally agree with Chris. I’m sad to see that postprocessors are misunderstood. I love postprocessors, but for me, cssnext is a preprocessor that is based on future (hypothetical) syntax. Postprocessors have to be implicit to improve CSS (fallbacks, etc.). Preprocessors have to be explicit (use their own language) to generate CSS. Preprocessors and post-processors work well together. And that’s why I’ve created my own tool Pleeease. :)