Java not that bad...

Java not that bad...

You know, Python will catch syntax errors at compilation. There are other errors (like mistyping a variable name) that C compilers do catch statically that Python only catches at runtime, but those aren't syntex errors. Looking back at all the bugs I've introduced in all the code I've ever written, none of the ones that mattered would have been caught by a C compiler. Perhaps your experience has been very different. Of course, much of my code had functional tests associated with it, which makes it a lot easier to quickly shake out the silly errors that C compilers catch but Python doesn't.

> I personally do *not* like python at all. Might be because I think
> interpreted scripting languages to be always a bad choice for huge
> projects - while they are second to nothing for smaller tasks!

Um, why do you "*not* like python at all"? I don't think its because Python is an "interpreted scripting language" because:

1. There are no Python implementations that are interpreted; they all compile Python code into code for a Virtual Machine, just like the vast majority of Java implementations. The VM code is "interpreted" in a sense, but exactly the same thing is true of Java code.

2. I have never seen an objective definition of the term "scripting language" and would be delighted if you could provide one; the closest I can come up with is that scripting languages have VM implementations that start up quickly enough to make running small programs from the command line feasible. That criteria includes Python and excludes Java, but I doubt its what you had in mind. In any event, having a fast VM hardly seems like a great deficiency.

I don't understand the line you're trying to draw between Python and Java at all; perhaps what bothers you is that one has static typing while the other has dynamic typing? To be fair, I don't think one can say that Java's type system is static given that it allows downcasting to Object and back...