Not quite. DLL Hell was the situation when apps installed their dynamically linked dependencies globally, so that when two apps shipped different versions of th

Not quite. DLL Hell was the situation when apps installed their dynamically linked dependencies globally, so that when two apps shipped different versions of the same library they could conflict. The situation was much rarer for dependencies because dependency trees simply weren't that deep in that era. It had also been solved since the introduction of assembly versioning over 20 years ago, which provided a standard way to have multiple versions of the same dependency installed and loaded side by side. Later Windows versions also added the ability to do the same for app-local DLLs, to the point where you can have different parts of your code get different versions of the DLL when they ask for it within the same process. So, for all practical purposes, it has been a solved problem for a very long time now.