3 ms·
For various reasons I would not go back to Java, but that was wonderful, your very old code still worked with newer versions, nothing broke during upgrades (eve
by _Codemonkeyism 9y ago
For various reasons I would not go back to Java, but that was wonderful, your very old code still worked with newer versions, nothing broke during upgrades (even when behind deprecation one version).
- pjmlp 9y agoWe do enjoy breaking changes every now and then. :) http://www.oracle.com/technetwork/java/javase/jdk-relnotes-index-2162236.html http://www.oracle.com/technetwork/java/javase/jdk-relnotes-i... Of course, they are never at the level of a Python 3 release.
- _Codemonkeyism 9y agoYes, but compared to e.g. Scala breaking changes in Java are heaven, thanks :-)
- cgdub 9y agoThere's a great talk about backwards compatibility in Java by Brian Goetz: https://www.youtube.com/watch?v=2y5Pv4yN0b0 https://www.youtube.com/watch?v=2y5Pv4yN0b0
- _Codemonkeyism 9y agoWatched, great talk, thanks!
- dilap 9y agoGo is really good about this too. It's great.
- andrestc 9y agoIt's not as strong as the kernel. Go does not break APIs but may break undocumented behavior.