Hi, 15 minutes is a better time frame. If the presenter cannot get across several good reasons why his/her language is "ideal" in 15 minutes, then an extra 90 minutes won't help.
Further, most people in the audience have had a long hard day at work - will they be up to long detailed talks on esoteric weirdnesses of a particular language? Reducing the time available forces the presenter to be concise and to the point. - which is good. Derek. On Tue, 17 May 2005, Michael JasonSmith wrote: > On Tue, 2005-05-17 at 11:47 +1200, Nick Rout wrote: > > Its not a suggestion for in depth exploration, but a quick and > > probably dirty comparison. > > > > stick to: > > > > bash, perl, python, ruby, php > I love the concept of having all the languages on one night, but I would > recommend 15 minutes per language (for a total time of 1.5 hours). > Harsh, but the only thing the presenters will be able to get across is > general concepts and enthusiasm; slides on the support of generic types > in dynamic languages and the difference between operator overloading and > parametric polymorphism will not be lost on most people (including > myself). > > I'll give a talk on sh/ksh/bash if no one else wants to give it a go. > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/
