When comparing CSS-Crush vs Garden (Clojure), the Slant community recommends Garden (Clojure) for most people. In the question“What are the best CSS preprocessors/postprocessors?” Garden (Clojure) is ranked 9th while CSS-Crush is ranked 14th. The most important reason people chose Garden (Clojure) is:
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.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Out of the box vendor prefixing
Rather than require a plugin, CSS-Crush will automatically add vendor prefixes.
Pro Implemented in PHP
PHP is used in common platforms such as Drupal and Wordpress, which results in CSS-Crush being easy to integrate with most development stacks.
Pro Style webpages with a full programming language
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.
Pro Full-stack Clojure with ClojureScript for front-end + Clojure for backend
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.
Pro Hot loading
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.
Pro Styles as data-nesting are obvious
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.
Pro Clean syntax
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.
Pro CSS-engine accessible from front-end
Because Garden is also Clojurescript friendly, this means that you can dynamically effect styles based on app state.
Cons
Con Not widely used
CSS-Crush is not a widely used option. The small community of users results in a harder time finding answers to any questions you may have.
Con Harder to apply shared styles
Because you are working in Clojure, you can't just paste in raw css style snippets shared elsewhere.