Oracle Hasn't Killed Java -- But There's Still Time 371
snydeq (1272828) writes Java core has stagnated, Java EE is dead, and Spring is over, but the JVM marches on. C'mon Oracle, where are the big ideas? asks Andrew C. Oliver. 'I don't think Oracle knows how to create markets. It knows how to destroy them and create a product out of them, but it somehow failed to do that with Java. I think Java will have a long, long tail, but the days are numbered for it being anything more than a runtime and a language with a huge install base. I don't see Oracle stepping up to the plate to offer the kind of leadership that is needed. It just isn't who Oracle is. Instead, Oracle will sue some more people, do some more shortsighted and self-defeating things, then quietly fade into runtime maintainer before IBM, Red Hat, et al. pick up the slack independently. That's started to happen anyhow.'
Re:Shenanigans! (Score:4, Informative)
Re: (Score:2, Informative)
I think that Java started to fail when it went into a split of Standard Edition and Micro Edition
Under Java 8 ME
http://www.oracle.com/technetwork/java/embedded/overview/javame/java-embedded-system-requirements-359229.html
* Alignment with Java SE 8 language features and APIs, enabling more streamlined creation of embedded software through a unified development model between Java SE 8 and Java ME 8
Oracle has been trying to fix that...
Re:Nobody kills Java (Score:4, Informative)
Complete nonsense. New upgrades have been carried out for COBOL, including COBOL 2002 which adds objects. There are several actively developed COBOL implementations. I think COBOL is more useful and available than its ever been.
Re:Pauses my 16 GB desktop working on 4K program (Score:3, Informative)
I can write a one-liner script that will bring a Unix machine to a crunching slowdown. Stupid in, stupid out.
If your little editor / mini-IDE craps out your machine, it is poorly written. Noticeable garbage collection will only be triggered if your Old Gen memory space is too full, which means you're maintaining references in memory which you should not (circular references are fun-- in someone else' code). Also possible is that it's simply not updating the UI while running a compile script, which is definitely bad programming. Blaming Java for that is idiotic.
Disclaimer: I write high-performance Java applications using Spring. Also maintaining a pile of spaghetti that has grown over the past ten years, that still performs adequately.