Hack programming language (Facebook's php++). They are called coeffects and can range from "this is pure with no side effect" to "this can modify local members" to "this has I/O".
It needs to be scoped to the dep so conflicting deps have independent dependencies.
If foo 1.1 takes a dep on Bar 1.2, and baz 2.3 takes a dep on Bar 1.4, both Bar contexts are tested with their respective libraries but forcing Bar to a particular global version can have problems and both versions of Bar are needed to have tested behavior.
Examples mentioned and OP change the global behavior vs proper dependency management.
Monkeypatching, dll injection, Jar Classpath - Huge sources of pain. It Is how it's done but in certain contexts any benefit is immediately outweighed as the bugs start accumulating.
One big realization I had how sophisticated the ancient world is, the Antithikara Mechanism. Device built by ancient greeks in 200BC using thousands of years of astronomical learning to build the first KNOWN Analog Computer and devices of similar sophistication are not seen until the late middle ages / early renaissance.
Never heard of tha but definitely going to check it out.
I kinda feel like that's how cities are today and will increasingly be so as we get further into the future where people are interacting digitally first and physically second interaction starts to stratify.
I imagine a holo-lens future where it's quite literally possible to have a city to yourself or only see the set of people you want to with all the good and bad. Imagine social media bubbles but in the real world, with all the good bad bad that comes.