To be successful however Clojure needs to adopt 'mainstream' values - introduce just one 'different' thing i.e. the language, rather than expecting people to adopt both the language, and a different development environment / toolchain e.g. leiningen etc (which IMO is classic NIH).
I think that depends on your definition of "successful".
If you think "popular with mainstream Java developers" is the definition of success, then yes: not scaring those poor folks is important.
I don't count that as success -- I call that popularity. I'd much rather have Clojure make me personally productive (and that means Swank, standalone REPLs, introspective debugging, etc.) than somehow feel validated because lots of faceless Java folks can get past some environment issue, only to reach the point of being scared away by the parentheses and immutable functional programming.
Ultimately, though, it all comes down to "here are some jars". If a Java developer can't figure that much out, they're probably not going to get very far regardless.
-- 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 To unsubscribe from this group, send email to clojure+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
