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.
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.
1
u/Programmdude Sep 15 '20
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.