Jon Pretty

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.

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.

I think the point is that Fury makes that easy. It will be a single command to move a source dependency out of Fury's private control and into your workspace to edit. Then you can fork and create a PR quite easily.

I agree there's an ongoing overhead if you're forever afterwards maintaining your own fork. That's probably not desirable for most people, but it may still be the difference between possible and impossible.

how? you're still going to get those users PRing your project with diffs to support their target, and they'll probably be displeased if you regress on their contributions.

Yeah, it is solved. The builds are external to the project, so it puts no burden on the project owner. The cost is potential fragmentation, of course, but it's a tradeoff.