posted 8 years ago
No point in "bumping" questions. We don't get paid so we answer when it's convenient. And if no one ever answers at all, it's either not been convenient or nobody knows. So just be patient.
Dynamic libraries have several benefits. They save disk space (no longer as big an issue as it used to be). They save RAM (still somewhat of an issue). And for complex functions, they can be upgraded to plug security exploits and fix bugs for a multitude of apps at the same time.
Windows originally had no idea of versioning on DLLs. There Could Be Only One. That led almost immediately to frustration with MFC.DLL and SOCKS. Ironically, at roughly the same time, the late, lamented Amiga OS understood the utility of having multiple versions of a shared libary and had included a version number as one of the criteria that an app would use for selecting one.
Linux/Unix also understand versioning, and use a 2-level (sometimes more) approach. You can open libtiff.so.5, or libtiff.so.5.2.2, depending on how necessary it is to reference a specific instance. Many times, less-specific library entries are actually links to more-specific ones, in fact.
If my fading memory doesn't fail me, Microsoft addressed this problem in .Net as well, but I haven't developed anything Windows-specific for a long time now.
Education won't help those who are proudly and willfully ignorant. They'll literally rather die before changing.