Random nugget of insight from @sjrdoeraene found while perusing unrelated threads: Source compatibility is broken in Scala when you *add a public method to a type*. Even ignoring diamonds, this alone is murder on source dependency schemes in this language.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
And this is precisely why I am the greatest detractor of Fury. But in some way I wish Fury all the technical success it can get, so that people can actually try it and see for themselves that an ecosystem based on source compat is not viable for Scala.
Though I still think you're envisioning that being an ecosystem where the sources can change behind your back and you end up with some unexpected maintenance. I'm not naïvely assuming that that would be practical.
