"The important question is, "Is Java dead for me?" " Great Point, "Is Java dead for me?" (and why or why not) would be an interesting question to ask HN regul

"The important question is, "Is Java dead for me?" " 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.