Great Point,
"Is Java dead for me?" (and why or why not) would be an interesting question to ask HN regulars, vs the stupidity of trying to decide whether Java is "dead" or "alive" in general. The former leads a personal statement of intent, and consequently there is no real argument about any answer. The latter is undecideable and leads to plenty of unproductive argument.
As for me, I just transferred the leadership of an Open Source Java library I maintain to someone else, primarily because I am sick of writing and maintaining Java. That said, it is just a personal decision and I can imagine many scenarios where Java (not just the JVM) use would be appropriate. I just hope I am never part of those situations again! :-)
Personally, when I need to build something on the JVM I'll use Scala or Clojure. Else, I'll use Haskell, Python or C as appropriate.
Touch Wood.
Generally, it's not a problem. I have a hard time articlating why, exactly... I guess my code just tends to be short, sweet, and to the point. It's very rare that when I code in C, for example, that I try to do something that the type system wouldn't allow anyway.
That's a terrible answer, my apologies. Maybe this would be better: could you provide an example of a situation where you feel that dynamic code would cause a problem?
Mabye a bit of back and forth will help me figure out what I'm trying to say.
Maybe it comes down to documentation. If I were to use some sort of function where I wasn't sure what the argument was, I'd look in the docs to see first.
Java is great for the enterprise because it's stable, mature, and doesn't leave any room for cleverness to fly over people's heads. However the compile-time checks don't do much to prevent difficult-to-debug errors. A more powerful type system like Haskell is much more interesting in this regard.
You definitely compile Java code well before you run it, at least in your full enterprise environment. And if you're using an IDE, you'll probably see any type errors well before you even compile it.
Sure, you might put your code through a workout with unit tests (and you should!), but any programmer knows that unit tests do not guarantee that you are using the right types in production, and they definitely do not ensure that clients of your code will be using the right types from your code.
I can't count the number of times I've had to use Data::Dumper just to figure out what type of object I'm dealing with. And don't even get me started with trying to figure out the right types of arguments to pass!
You are correct that the hardest bugs will be left for run-time, but why add to the hassle?
It's like proclaiming conventional spanners dead now that you can get adjustable spanners.
Some jobs you want solid object based exception handling water tight programming, and other jobs you want loose runtime based functional stuff.
I think in the end, the author really nailed it. The important question is, "Is Java dead for me?" I would not use Java for a new personal project (and probably not for a work project either unless the libraries were needed). I do not have a clear replacement in mind... Python stands out the most.
My biggest problems with Java are the compilation step (admittedly not that big a deal with an IDE, but I don't always like to use an IDE), the insistence on objects, and most importantly, the lack of first class functions.
A new issue that has come up for me in comparison to Python is constructor overloading. In Python, constructor overloading is beautiful because of args and kwargs. In any C-family language (including Java here), it's horrible. With small objects where inheritance works well, the constructors in other languages can get unwieldy fast. In Python, they're always concise. I also love keyword arguments in general. It can make code much more readable, especially when using something like wxPython, where the parameter lists are long and otherwise would be quite vague.