3 ms·
Extrapolating from the post that Clojure tooling is bad seems like a strange conclusion. I'm actually surprised that such a narrow post would find this much int
by swannodette 12y ago
Extrapolating from the post that Clojure tooling is bad seems like a strange conclusion. I'm actually surprised that such a narrow post would find this much interest on HN.
Clojure deploys are pretty ridiculously easy - and refreshing pages on a Clojure based web stack is also instantaneous.
Seriously, Leiningen is great tooling. On pretty much every axis except startup speed I prefer it to everything else I've needed to use for work in other languages (Python, Ruby, and Node.js).
- phren0logy 12y agoI wholeheartedly agree. I wish every language had a Leiningen equivalent, despite the speed issues.
- pandeiro 12y agoHear, hear. I long for the day that lein and cljs tooling can replace bower/npm/grunt/gulp entirely. And I came to Clojure(Script) from JS, not Java, still have no clue what maven or pom.XML even means, but lein obviates all of that. The main criticism I'd make, and this is something the boot (http://boot-clj.com http://boot-clj.com) guys have mentioned (http://c2.com/cgi/wiki?CodeGenerationIsaDesignSmell http://c2.com/cgi/wiki?CodeGenerationIsaDesignSmell), is that we are getting pretty dependent on code generation with lein templates, and they are getting increasingly larger and more complex just to handle our base scenarios (dev/prod builds, REPL, live reload). Maybe this is unavoidable, or not really an issue... I don't know.