How about something from the world of concurrency? It is not as easy to demonstrate, though. Many true advantages are too subtle for elevatorspeak, though. For example, people used to pitch *pmap* that way: instantly turn a sequence transformation into a multicore-saturating performance king. The reality is that there are increased constant-time-and-space costs involved and there are major issues with chunked seqs.
Another similar thought is transforming an arbitrary calculation into a * future*. When I pitch Clojure, I use as much emotional arguments as rational ones, and I see many others feel the same way: the *joy of Clojure* is something many people feel. Sharing your enthusiasm works quite well in the field :) On Wednesday, January 16, 2013 4:08:41 PM UTC+1, 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
