> What does backwards compatibility mean to me? > I want to not spend much time upgrading a dependency > Go compatibility promise: >So whenever a change in b

> What does backwards compatibility mean to me? > I want to not spend much time upgrading a dependency > Go compatibility promise: >So whenever a change in behavior happens in an upstream library You are comparing a promise from language designers to no promise from the library developers. Syntax from Oak (before Java was called Java) still compiles and works in Java 17 right now: jshell pub| Welcome to JShell -- Version 17 | For an introduction type: /help intro jshell> public abstract interface I {} | created interface I You can still type (public abstract interface - all interfaces are abstract by default since Java 1) and it works. One of the reasons I gave up on writing desktop applications in Go was libraries were breaking compatibility with every commit. GTK+ binding was literary unusable as before gomod this would break literally, and I mean literally, every day. Please tell me that none Go library had any breaking changes in the last 5 years and I'm using it as my default ecosystem from tomorrow.