Re: Programming language productivity

2006-05-21 Thread John Bokma
Peter Maas <[EMAIL PROTECTED]> wrote: > John Bokma wrote: >> Also note that Python programmers write more lines/hour which they >> need to finish in the same time as Perl programmers :-D. > > You probably want to say that a Python program tends to have more > lines than an equivalent Perl program

Re: Programming language productivity

2006-05-21 Thread Edward Elliott
Peter Maas wrote: > I think that a LOC comparison between a language that enforces line breaks > and another language that enables putting an lots of code in one line > doesn't make much sense. I wonder why comparisons aren't made in terms of > word count. Word count would include literals, consta

Re: Programming language productivity

2006-05-21 Thread Peter Maas
John Bokma wrote: > Also note that Python programmers write more lines/hour which they need to > finish in the same time as Perl programmers :-D. You probably want to say that a Python program tends to have more lines than an equivalent Perl program. I think that a LOC comparison between a langu

Re: Programming language productivity

2006-05-19 Thread Jack Diederich
On Fri, May 19, 2006 at 02:21:39AM -0700, malv wrote: > Once you get involved in larger projects, the dynamic nature of the > programming tool becomes much more important. I mean by this, the > ability to stop running code, modify or add to it and continue without > having to re-establish the state

Re: Programming language productivity

2006-05-19 Thread Harry George
"malv" <[EMAIL PROTECTED]> writes: [snip] > Once you get involved in larger projects, the dynamic nature of the > programming tool becomes much more important. I mean by this, the > ability to stop running code, modify or add to it and continue without > having to re-establish the state of the pro

Re: Programming language productivity

2006-05-19 Thread malv
John Bokma wrote: > Connelly Barnes <[EMAIL PROTECTED]> wrote: > > > http://barnesc.blogspot.com/2006/05/programming-language-productivity.h > > tml > > C:3 hours to write the program, 5 hours to track down the memory leaks > Java: 4 hours to write the program, 6 hours to get all the exception

Re: Programming language productivity

2006-05-18 Thread John Bokma
Connelly Barnes <[EMAIL PROTECTED]> wrote: > http://barnesc.blogspot.com/2006/05/programming-language-productivity.h > tml C:3 hours to write the program, 5 hours to track down the memory leaks Java: 4 hours to write the program, 6 hours to get all the exception handling right C++ 5

Programming language productivity

2006-05-18 Thread Connelly Barnes
Hi Python folks, I created a summary PDF of two studies on programming language productivity: http://barnesc.blogspot.com/2006/05/programming-language-productivity.html One notes that Python and Perl are the two best languages by the "number of hours to solve problem" metric.