The most important layer in dependency management, I've found, is always in the systems code and what resources it consumes. If you get a handle on that, the re

The most important layer in dependency management, I've found, is always in the systems code and what resources it consumes. If you get a handle on that, the rest is addressed with a well-targeted interface to the systems code, which the application uses uniformly. This interface can even take the form of a transpiled language. And to the degree that Rust is effective, it lets a greater portion of the systems code be managed by a common interface. It remains as painful as most when it comes to binding external C code. (I do think Zig is really promising in this regard by aiming to absorb C more comprehensively.)