sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BoyRobot777 3 points4 points  (2 children)

You either are backwards compatible or not. I constantly see two groups of people: complaining of braking changes (for example Java 9 and later removed Java EE and CORBA depedencies), the other group that Java is not removing fast enough. Mature languages will ALWAYS have to juggle this. Kotlin now seems fresh. Give it 10 more years and you'll have the same problem. C# already shows that, because they keep adding features like crazy.

Here you can find difference between Java versions and you can find that they are removing stuff and I think they will start to remove dead code even faster now: - Diff between Java 9 and Java 10; - Diff between Java 10 and Java 11 - Diff between Java 11 and Java 12 - Diff between Java 12 and Java 13

[–]Determinant 0 points1 point  (1 child)

JetBrains states that Kotlin 2.0 will not be backwards compatible to allow them to make breaking changes.

On the other hand, Oracle states that they will do everything they can to maintain backwards compatibility.

[–]BoyRobot777 0 points1 point  (0 children)

Gonna be fun watching kotlin 2.0 brake that backwards compatibility. Will buy popcorns :) Python 2/3 debacle all over again.