Programmers have been tossing the word Enterprise around for decades, like it means something. Quit it already. You're embarrassing yourself. Many so-called En

Programmers have been tossing the word Enterprise around for decades, like it means something. Quit it already. You're embarrassing yourself. Many so-called Enterprise Java apps often don't work at all unless you've installed the /exact/ JRE version that the particular app supports (Looking at you, Citrix). The fact is, that it was a dying language before Android. Hopefully it will resume dying, and Google will either release something better, or embrace an existing Open Source community like JavaScript, Ruby, or Python. (Edit: Now that I think about it, Google's own V8 JavaScript engine would be well suited for this. It already supports ARM Linux.) Personally, I was forced to take 2 Java classes in college. The examples in our labs never worked. I had to Google everything in the book to make Java code that actually ran. Swing looks the same as it did in 1996. Everyone at the local JUG was considerably older, and spent most of the time complaining about what a pain SVN was. (A clue: You're doing it wrong.) Despite all of this, I was still learning to program, and actually sortof enjoyed it. But then Sun got acquired by Oracle, inventors of the only database system that makes me want to kill myself. After that, I started seriously considering other languages. But the real nail in the coffin was when Oracle decided to cockblock Apache Harmony, and Apache stepped down from the Java Committee. For shame, Oracle. After all nice things Apache made for the Java Community. How fitting, that Google used Harmony code to create Dalvik, the Android VM.