Java SE 6 and 7 devs weigh their options as support ends Oracle Java Development Kit 6 and 7 support ends this week, leaving a sizable chunk of developers looking at their options. Around 15 percent of Java developers still use JDK 7, according to a survey by JRebel, which produces its own code development environment. That being the case, around a million developers could end up …
The "Java 2" thing _was_ confusing but you're looking back more than 2 decades here. Since then we had 1.5, 1.6, .... and then by convention we dropped the "1." because it was getting retpetetive... not too hard.
Othe version cadences such as 1, 2, 3, 3.1, 3.11, 95, 98, ME, 2000, XP, 7, (*expletive*), 10, 11 come to mind.
Big corps on Java 6/7 have tons of in-house tooling to modernize the language. Jump forwards to Java 17 and it's modernized already, but not in the same way. 15 years of custom tooling is redundant yet not mix-in compatible.
If you're going to pick a rapidly evolving programming language, you should probably update your compiler every few years.
> If you're going to pick a rapidly evolving programming language, you should probably update your compiler every few years.
Not meaning to start a flame war or cast a judgement on whether this is a good thing or not but... are you really calling Java a "rapidly evolving programming language"? Java?
I think C++ of all things has a higher rate of change.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2023
