@fiore @hipsterelectron @Lightfighter @TodePond it gives you total control over what exact version of dependencies you get rather than deciding for you, allowing you to use fixes and shims
it's kind of like how dynamic typing allows you to do wild shit with the types of your data (though most developers probably cannot be trusted with that kind of power)
@SRAZKVT @fiore @Lightfighter @TodePond RIP to them but i'm different. and better. maybe better than the gods
@fiore @hipsterelectron @Lightfighter @TodePond i do think languages that insist on having their own package managers and build system should have a way to generate a project template to build shims as well as a way to cross run tests for compatibility checks and edge cases
@SRAZKVT @fiore @Lightfighter @TodePond this should be a general feature of a build system
@SRAZKVT @fiore @Lightfighter @TodePond spack has external packages for things outside of its system which is the single biggest problem i find with guix-like systems that they can't integrate external code and they don't really contribute to interoperability at all as a result
Oct 15, 2026, 4:52 AM@SRAZKVT @fiore @hipsterelectron @Lightfighter @TodePond assuming everyone is following semver & nobody is relying on implementation details, this shouldn't be an issue
@solonovamax @fiore @hipsterelectron @Lightfighter @TodePond people will rely on implementation details, that's why cross run tests, running og tests on shim and vice versa
@solonovamax @fiore @hipsterelectron @Lightfighter @TodePond as for semver, it imo should be automated (though with tighter interface contracts) bc people fuck up