Garden (Clojure) vs cssnext

With Garden, you have access to all the core features of a powerful programming language to build your scripts, including functions, variables, namespaces, and data manipulation like map merging or concatenation.

Garden finishes the full Clojure stack experience — you can have the entire codebase in a single language with ClojureScript on the front-end, Clojure on the backend, and Garden for CSS.

Using the core Garden auto loader or the excellent Garden Gnome plugin, watch your style changes take effect in the browser as soon as you save the code — no reload required.

Clojure is a data-oriented programming language with strong emphasis on simple, clear inline data structures. Garden models styles using these same structures, making the cascade visually obvious.

Other options listed include various pain-points like use of @ symbols or too much cruft; because Garden is just Clojure, and Clojure is a very well-designed language aimed to emphasize simplicity and positive developer experience (without semantic whitespace problems), you have the full benefit of a well-designed and general-purpose syntax.

Because Garden is also Clojurescript friendly, this means that you can dynamically effect styles based on app state.

cssnext is a PostCSS plugin, which makes it pretty easy to use for people who are already using PostCSS.

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.

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.