Java != JVM
Posted Mar 14, 2004 9:51 UTC (Sun) by joib
In reply to: Java != JVM
Parent article: Will Mono Become the Preferred Platform for Linux Development? (O'ReillyNet)
On the other hand Python is often too dynamic and many errors that would be caught in a staically typed language are happen at run time.
Personally, I think that static typing has its place, and that is in low level high performance languages like C/C++. For writing applications in a high level language like Java or python the argument is much weaker.
Write any non-trivial program in Java and it's almost certain that you'll make extensive use of the collections classes. Well gee, say goodbye to your type safety. The only thing that static typing gives you here is lots of type casts all over the place (Ugh!).
But I don't worry that much about the loss of static type safety. Unit tests (you do practice test driven development, now don't you?) will catch type errors, among many other things.
Java even with its language design problems and even with only features available currently in GCJ fits network-bounded-server role resonably well.
Personally, I would like to use python for this task too. But what saves Java, is that there is *a lot* of very high quality open source stuff for almost anything you can imagine. For starters, the spring framework and hibernate will take you a long way towards server-programming nirvana, despite the "over-verbosity" of Java. The only thing in the python world that even comes close is zope, and that is IMHO a bit too weird and un-pythonic. However, zope 3 does look promising, and I'm planning to take another look at zope once it's released.
to post comments)