The duck streams library should give some examples the Java crowd will be ready to appreciate. That, or maybe use the with-open macro.
My $.02 On May 21, 7:42 am, Rich Hickey <richhic...@gmail.com> wrote: > On May 21, 3:39 am, mikel <mev...@mac.com> wrote: > > > > > On May 18, 7:36 am, Rich Hickey <richhic...@gmail.com> wrote: > > > > I'll be doing two sessions involving Clojure at JavaOne this June. One > > > is a traditional talk (TS-4164), the other is as a participant in the > > > Script Bowl 2009: A Scripting Languages Shootout (PAN-5348). > > > > The 'script' bowl is a friendly competition, basically a place to show > > > off your language and seek audience acclaim. > > > > "Scripting language gurus returning from 2008 are Groovy, JRuby, > > > Jython, and Scala. This year there is also a new kid on the block: > > > Clojure." > > > > There are two very brief rounds, 4 minutes per language each round . > > > > round 1: Core language and libraries round (show something really cool > > > with the core language and libraries) > > > > round 2: Community round (show some significant community > > > contributions) > > > > Note there is no comparative aspect, each language presenter talks up > > > their own language and the audience decides, so it's not an > > > opportunity to draw contrasts explicitly. It's about being pro- > > > Clojure, not anti- anything else. > > > > The audience is Java developers, many of whom will have never seen > > > Clojure or any Lisp. > > > > I'd appreciate some suggestions *and help* preparing demos for the > > > Script Bowl. What (that could be demonstrated in 4 minutes) would make > > > you think - 'Clojure looks cool, I need to look into it'? What > > > community contribution(s) should we showcase? > > > Show something that does a lot of visible work quickly with very > > little code, where the code is still very readable and easy to > > understand. > > > Show how to do something that Java programmers have to do pretty > > often, and that requires many lines of code, but which requires very > > few lines of code in Clojure, yet the code is still very > > understandable. > > > Show how someone can look at a running demo and ask for a different > > feature, and you can implement the feature and have it show up in the > > running demo without needing to stop and restart it. > > > Show how you can run a demo with a bug in it, trigger the bug, to > > cause a break, fix the bug while in the break, and resume the demo > > with the corrected code. > > > Show how you can do all of this from a nice interactive session, but > > also quickly and easily package the demo app as a jarfile that you can > > deploy like any other jarfile. > > > Show how easy it is to look at the guts of any Java instance or class, > > and how easy it is to instantiate and use classes and interfaces. > > > Take a concurrent Java example that exhibits hard-to-debug threading > > issues (this should address pain that any server-side Java programmer > > has felt), and show how they go away in the presence of Clojure's > > safety guarantees. > > > Finally, show them that they don't lose performance by gaining these > > features. > > And in the second 4 minutes? :) > > Rich --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---