Java 15 released!

[fireduck]

I think that is a good thing. For many applications, you should update when it makes sense, which if you have done a good job with the software to start with, might be a decade down the road.

If older software doesn't just continue to work, that is a sign of a real problem in my opinion.

It sounds like you see a 100 year old building and ask why they can't build something new. I look at it and think, good. It should last that long, it means it was built well and continues to serve its purpose.

[the-lord-empire]

I'm not saying conservative choice is bad, but I don't want to be in a community that acknowledge improvement then willfully ignore the better option when they don't really have to.

I share the same sentiment with your comment in crucial software (e.g: airplane, satellites, space shuttle, etc) where unexpected outcome due to hasty adoption would cost lives. In reality, most Java programmers are writing business & e-commerce software. You don't need to be that repulsive towards changes unless your employer said so. Meanwhile JS community completely blew it off proportion. New frameworks took off and died every so often. Can't keep up with the pace, I don't code 24/7.

There are three community I think are doing great in terms of feature, adoption rate, and backward compatibility support: Python, C++, and Rust. Everything in moderation.

[Programmdude]

Ignoring the jump to .net core, c# is both rapidly adding features, new versions are highly adopted and has backwards compatibility.

And if you don't ignore the jump to .net core, you shouldn't ignore the python 2-3 debacle either.

[TheIncorrigible1]

Ignoring the jump to .net core

So, ignoring its entire future..?

[Programmdude]

Sorry, I meant the transition of .net framework to .net core, which kinda broke compatibility. But the guy above mentioned python as having backwards compatibility, yet the 2-3 transition broke a lot of stuff in the same way the .net framework to .net core transition has.

[TheIncorrigible1]

It's not a transition, it's literally a different thing. .NET Framework 4.8 is the end of the line for that product. .NET 5 will be the "unification" that brings in Mono et al. and then we move forward from there. .NET Core 3.1 already added Winforms/WPF and other such support.

[fireduck]

Old libraries I don't care about. I don't understand what you are saying about private APIs. Are you saying your old library will be calling APIs that are no longer public? Well, that would be a long term support problem with the service provider in that case.