Patrick Hurley
3/17/2005 2:01:00 PM
Two thoughts:
1. Also suggest to the language designer that they can delegate the
task, they may not have the time nor the desire to participate, but
will likely know one or two people who do.
2. As much as I hate to say it, for experienced developers lines of
code are a pretty reasonable rubric for development time (and even
more so for maintenance). This can of course be abused when extra time
is used to compress the code into fewer lines. But if the code is
immediately understandable by another developer of the same language
(which is of course open to significant debate as well) then the LOC
is a useful measurement.
On Thu, 17 Mar 2005 22:50:03 +0900, Curt Hibbs <curt@hibbs.com> wrote:
> Robert McGovern wrote:> Sent: Thursday, March 17, 2005 7:11 AM
> > To: ruby-talk ML
> > Subject: Re: new language shootout
> >
> >
> > > > BTW, I wonder how do you think to rate the time required to implement
> > > > something. I could take a week to write a quicksort in ML,
> > but probably
> > > > an MLer could do that in one minute.
> > >
> > > I don't really know right now, but any suggestion is very welcome. Maybe
> > > I just try to find nice programming tasks where design really matters
> > > and performance is pretty irrelevant, and just present the solutions
> > > without any rating.
> >
> > Get the creator of each language to write the code? Really come up
> > with a decent small but complex task and approach Wall, Gosling, Matz,
> > Guido, Straustrope(?) and so on and ask them if they would be willing
> > to participate. They could use whatever novel approach their language
> > affords for doing it, it would be interesting to see the results.
>
> Nice idea! Don't forget Alan Kay (Smalltalk), as well as OCAML and Haskell
> (I don't know who created those).
>
> Curt
>
>