"Besides the languages itself, the "outsider" wants to evaluate libraries, community, platforms, support, etc. That could be much more challenging than comparing a few bare languages."
Absolutely! I asked a couple of times for recommendations, and was quite surprised at the lack of forthcoming recommendations. The dilemna that I am for-ever battling is "get something done in a poor way now" or "invest in something so we can do it better in the future". Adopting Clojure is definitely in the second camp (for me), and the lack of knowing which supporting libraries (for example) to use makes it more of an expense. Of course, what I want to do is plough that ground myself and produce a single "101 Enterprise Clojure Development" but time time time. The professional me wants/needs it done for me, the geek in me wants to do it myself and give back to the community. (since I opened the door :)): my current thoughts are: - clojure 1.3 (complete with integration pain with 1.2 libraries) - maven 2 (with maven 3 polyglot once it is stablised and publicly available) with the clojure-maven plugin - bamboo (hence the maven decision rather than cake or lein) for CI and release management - cucumber for higher level "does it do the requirements" tests (not getting hung up on the highly overloaded testing terminology) - lazy-test for "does the code do what the developer expects" tests - emacs/slime for coding - some ring based web framework (probably clojure) - either mongodb or a graph database for persistence (need to determine the inter-relatedness of the graphs) - the venerable git - one of the gazillion high quality Clojure libraries on github As an enterprise developer I need to be able to come to those conclusions myself, of course, but some sign posts would be very useful. http://planet.clojure.in/, http://ericlavigne.wordpress.com/2011/01/30/a-tour-of-the-clojure-landscape/ , http://www.clojure-toolbox.com/ etc. are very useful points. The more I look, the more I am extremely impressed by the high quality blogs around Clojure, in particular http://cemerick.com, although that is one of many. (still only 3 lines of Clojure written!) On 12 July 2011 13:55, Sergey Didenko <sergey.dide...@gmail.com> wrote: > You know that from inside. A Clojure "outsider" can have a completely other > point of view. > > He can choose between Python, server side Javascript, new C#, Go, Scala, > F#, Haskell, Erlang, haXe, Clojure. > > Besides the languages itself, the "outsider" wants to evaluate libraries, > community, platforms, support, etc. > > That could be much more challenging than comparing a few bare languages. > > > On Tue, Jul 12, 2011 at 11:25 AM, Ken Wesson <kwess...@gmail.com> wrote: > >> > When people are looking for a new shiny thing among 100 of other just >> new >> > things, they can turn into "scanning mode" despite the fact that in >> other >> > conditions they " do >> > that sort of "analytical comprehension" " >> >> What other new shiny languages are there with any traction? Scala, and >> maybe F#? > > > -- > 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 > -- 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
