Hi,
On 7/17/06, Prem Kurian Philip <prem@xxxxxxxxxxxxxxxx> wrote:
I have written and architected some very large enterprise applications in
Python: if I am asked to do something similar now, I would definitely go
with a language like Java. The problem with java is not the language but
rather the overly complicated mess that is J2EE and this crazy fixation
with "descriptive programming" using a million XML files for even
describing application logic. J2EE looks like it was designed by a
committee and it most certainly was.
The time it takes to compile code is quite often overstated. The compile
process reveals errors which can then be fixed quite easily. In a
dynamically-typed system, you will have to deal with the same errors but
you will discover them (if at all) only at runtime - and so what you lose
in compile time (on statically typed languages) is more than exceeded in
time it takes to discover the errors while programming using a
dynamically-typed language.
Also, the performance penalty of dynamically-typed languages may not be
suitable for some applications.
I am no purist - I continue to use languages like Python and Ruby (and on
occassion, groovy), but not for the large scale applications where java /
.net is more suitable.
