Before 0x, Java didn't matter for production code as the 1.3 with JIT came later than that.

But in those days it was a big mess to write portable C++ code, given the discrepancies between compilers.

I don't miss those CORBA and DCOM libraries, but I miss OWL and VCL.

Java is still quite strong in the Fortune 500, and most managers don't care about Oracle vs Google, as it was caused by Google trying to avoid to pay Sun anyway.

However I sense some signs similar to when CA started loosing CLIPPER's direction, or when Borland attitudes started scaring people away from Delphi and C++ Builder.

On the other hand, Java is just too big and it will take generations to replace all those systems.

The earliest version of Java I worked with in production was 1.5, but the group I was working with had been using it in production a long time before that. There were other groups using Java for a lot of other things (JDBC, JMS, etc...). All the stuff I worked with relied on core Java and NIO though, which I'm not entirely sure how a lot of things were done before 1.5.

Java is definitely still really popular for development overall (TIOBE 2015 #1). My personal concern with Oracle vs. Google though is that Oracle does not own the language, and the copyright claim on APIs seems pretty aggressive. The JVM and Java have open specifications which in theory anyone should be allowed to implement (practice is admittedly a bit different). Even the official JDK was open source, which Oracle seems a bit hostile toward considering what they've done with purchases like MySQL and how the community largely responded.

Claiming copyright on an API seems somewhat akin to Keurig 2.0. Although, I think courts are having trouble keeping pace with technology.

I have been using occasionally Java since it was made available in 1996.

Our university adopted it right away and made it in 1997 the official language for compiler development and distributed systems classes.

Without bothering to search the Internet, NIO was either introduced in 1.4 or 1.5.

Yes they have open specifications, but they also have trademarks and compliance certifications.

The JDK was open source, but the license prevented its use for mobile devices without a Sun approved license, that Google didn't want to pay for.

So now Google has actually created a fork in the Java community.

Just imagine when you have Java 9 with modules, or Java 10 with reiffied generics, value types, JNI replacement, official unsafe package, among many other roadmap features, how to keep the code portable between Android Java and the real Java.

You are right, but google is moving to OpenJDK. This will fix those problems, or did I misunderstand what the implications of this move will be? http://venturebeat.com/2015/12/29/google-confirms-next-andro...

edit: The article does state at the end that google will still modify OpenJDK for their own needs, but that still means that the vast majority of the implementation will be the same, so this seems to avoid most incompatibility issues.

Thanks, I actually missed this. The difference with modifying OpenJDK is that it's a common codebase as opposed to a language fork.

I know Redhat is one of the other major OpenJDK contributors, and a lot of distributions are relying on IcedTea. It will be interesting to see how this develops.

So far Google has adopted parts of OpenJDK 7.

They still don't tell anything about newer versions.

NIO was 1.5. Before that, a lot of network programming wasn't practical where performance was a concern. I would guess it was the same with Linux before 2.6.