Garden (Clojure) vs Pleeease

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.

preprocess CSS (experimental)
adds prefixes, based on Autoprefixer
provides fallbacks for rem unit, CSS3 pseudo-elements notation
adds opacity filter for IE8
converts CSS shorthand filters to SVG equivalent
packs same media-query in one @media rule
inlines @import styles
minifies the result
generates sourcemaps from pre- to postprocessors

If you have repeated media queries in your stylesheet, Pleeease will pack them into a single media query when compiled.

Rem unites are not supported in IE8 and below, so Pleeease provides a pixel fallback.

Pleeease uses Autoprefixer to add vendor prefixes based on which browsers you want to support (prefixes are added based on information from caniuse.com.