> Windows doesn’t have global library folders that are polluted by a million user scripts. C:\WINDOWS\SYSTEM32 It's called "DLL Hell" for a reason. It used to

> Windows doesn’t have global library folders that are polluted by a million user scripts. C:\WINDOWS\SYSTEM32 It's called "DLL Hell" for a reason. It used to be very common for every program you installed to dump several libraries in that directory. It included program-specific libraries (so that directory would have a mix of internal libraries for every program you ever installed; pray there were no naming conflicts!), compiler runtime libraries like the C library (and it was not uncommon for a program to overwrite an already existing runtime DLL with an older version, breaking other programs which expected the newer version), and sometimes even operating system libraries. It got so bad that IIRC Microsoft made Windows automatically detect when an important operating system DLL had been overwritten, and restore it from a secret copy of the original DLL it had stashed elsewhere.