Unlike other older languages, such as Cobol and Fortran – which are still used, but almost always in legacy projects – Java has constantly evolved to meet new demands while maintaining backward compatibility.
can’t speak on the FORTRAN claim but with COBOL this couldn’t be less true. last i checked the newest Enterprise COBOL LTS is newer than Java’s
People aren’t writing new projects in COBOL. It’s mostly to maintain 40+ year old systems. Unless you’re working in the bank sector, it’s unlikely you will write a program in COBOL.
Yeah, I know that the vast majority of Java applications out there are stuck on ancient versions of the JVM and spew back traces in their logs as if they bought them in bulk.
can’t speak on the FORTRAN claim but with COBOL this couldn’t be less true. last i checked the newest Enterprise COBOL LTS is newer than Java’s
The difference is people still write Java, regardless of whether it’s a dated pos or not, so the use cases have evolved
Then there’s the use of the JVM/JRE which have evolved even more due to Scala, Clojure & Kotlin
COBOL is still being updated because, believe it or not, people are still writing COBOL
People aren’t writing new projects in COBOL. It’s mostly to maintain 40+ year old systems. Unless you’re working in the bank sector, it’s unlikely you will write a program in COBOL.
Don’t forget this small sector called government. Loads of Cobol there.
And Java is very much considered legacy in the vast majority of projects that use it.
Then it would not be constantly evolving with more than a new release per year. Do you know anything about gigantic Java ecosystem? Guessed so …
Yeah, I know that the vast majority of Java applications out there are stuck on ancient versions of the JVM and spew back traces in their logs as if they bought them in bulk.