On Wed, 10 Nov 2004 10:16, Martin van den Bemt wrote:
> > Dare I repeat the old adage? Java: write once, debug everywhere.
>
> Write once is still the truth. Progress, bad programming (eg not being
> binary compatible in new releases) and not keeping up-to-date �with
> dependencies as a programmer results in debug everywhere (this aside
> from finding bugs)

I must say I have found programming Nirvana in Python - even the most complex 
server application / web services can be written in maybe a third of the time 
it takes in Java, and most code runs first time after writing without even 
needing to go through a tedious debugging process.

Yes, there is a small performance penalty. But that's more than made up in the 
form of saved man hours and robustness.

And, as opposed to Java, Python truly runs everywhere after writing it once. 
Close to zero portability problems, as long as no GUI involved.

Seriously: what can you do in Java that you can't in Python nowadays? So why 
then the extra effort it takes to do it in Java?

Horst

Reply via email to