DEV Community

Discussion on: Java is Dead - Long Live Java

Collapse
 
gajatko profile image
Jacek

It's fun how you get excited about upcoming (or not)features of Java which have been in C#, like, for years. And we're still coding in a language where comparing two same strings might result in false... and you have to use "add"or "subtract ( )" methods instead of operators. Java is dead on the inside, like a zombie

Collapse
 
michelemauro profile image
michelemauro

The recent 6-months release cycle is trying to reverse the trend that started in the early 2010. Java was far ahead of C# until 2011-2013 maybe, and then remained still for years waiting for 7 and 8 while C# was first reducing the distance, and the hopping forward in leaps and bounds. Now we're closing in again, and the JVM platform is already so competitive with the .Net one that choosing one or the other is a matter of available skills or choice.

The JVM is stronger than ever, and getting all the latest in innovation and research. Java is playing catch-up with both the internal (Scala, Kotlin) and external (C#, F#) competition, but its appeal as boring, dependable technology is far from gone.

Collapse
 
stealthmusic profile image
Jan Wedel

Great summary 👍

Collapse
 
stealthmusic profile image
Jan Wedel

As I said, it's actually not a problem that other languages are ahead and try things out. That's certainly no reason to switch to a new language.

To your other points:

  • == compares references so every Java developers knows after month or so to use .equals().
  • I consider operator overloading actually harmful but YMMV.

But my article was not intended to convince you to use any other language. Use the tool you're happy with.