I think it depends a lot on your audience. For example, java spring programmers are likely going to be impressed by the simplicity and speed at which you can get a project started, especially when using lein and being able to avoid the common load of bolerplate java, xml, etc. Programmers familiar with database development etc, may appreciate the STM more, lisp programmers will likely be impressed by how easy it is to take advantage of the huge wealth of existing Java APIs and managers may be impressed by the fact things can be deployed under the existing ecosystem.
There is no single answer, but a little research into what type of audience you are addressing will help. Try and find out what some of the current 'pain points' are with their current environment. This could be testing, it could be deployment, it could be the ability to make rapid changes, handle concurrency issues, prototyping, cumbersome code, build test cycles etc. If you know this, you can structure examples that will clearly show the relevance and likely generate some excitement etc. Tim On Thursday, January 17, 2013 2:08:41 AM UTC+11, Thomas wrote: > > Hi All, > > Something that came up last night in the blank? thread. What is a good way > to show someone the advantages of Clojure. Something that is simple, not > too complicated, easily understood, shows a (significant) benefit, etc. > > Any ideas? (As said in the other thread, I have used the blank? example > from Stuart Halloway to show people the difference). > > Thomas > -- 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
