> > I do not think we should attempt a recommended IDE (not even Clooj). > We should offer a path for all existing IDEs / editors. > ...
> Use an editor not listed here? Try Clooj > (i.e., use this as a simple catch-all if we haven't covered what you > already used today). > That's one way of organizing it. The slightly serious explorer will of course pick setup documentation for their favorite IDE/editor, and that should be provided. But think of the casual dev wanting to know what Clojure and a typical Clojure toolchain can do for her ASAP. Most Java devs have never used a repl-aware edit buffer, something most of us take for granted. No common IDE/editor setup can expose her to a lisp-style toolchain in a single click. None. For usability, nothing beats the single-click. In seconds, Clooj gives her a one-stop-shop. So I see Clooj as something worth putting right along with try-clojure.org. It not only showcases Clojure, but is rapid exposure to the lisp-style toolchain. That's why I would give Clooj some prominence rather than burying it at the bottom of the decision tree. Anyone knowing what they're looking for will of course move on to the setup of their preference (emacs,vi,eclipse), so they don't lose anything. But the neophyte who doesn't know what they're looking for should have the lowest barrier to entry possible - usability. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
