If you go the source dependencies way, you cannot add a public method to any of your types, ever. Because that breaks backward source compatibility. Yes, binary compatibility is hard. But source compatibility is *impossible*.
But source compatibility is *safe* (the compiler checks it), whereas binary compatibility is *risky*. Composing a classpath at the same time as compilation guarantees there's no mismatch between the two... at the not-insignificant cost of having to compile the world.
-
-
This Tweet is unavailable.
-
I don't understand how you can "fix it right there and then" for source compat any more than for binary compat. In both cases, you'll have to fiddle with your dependency's source code, which means forking it in either case.
- Show replies
-
-
-
Binary compat is also safe if your dependencies apply MiMa. And it can be safe in the same way as source compat if someone would just write a link-checker for the JVM (~1 week of work, and maybe Proguard even has an option for that, and I've heard JDK 10 has a tool for that too).
-
This Tweet is unavailable.
- Show replies
New conversation -
-
-
I'm not an expert Nix user, but I wonder if wrapping Nix (or reimplementing it) could solve many such problems. Maybe that's largely what Fury is doing, haven't had a chance to read about it yet
-
That's my fault, though! All I've done is one talk announcing it so far... I don't know Nix well, but I think Fury is different enough and simple enough not to be just a wrapper around Nix.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.