2 ms·
Yes, so that one component can be upgraded and be used by other programs. Recall the zlib bug of a few years ago. Everybody who linked zlib statically had to pr
by roel_v 16y ago
Yes, so that one component can be upgraded and be used by other programs. Recall the zlib bug of a few years ago. Everybody who linked zlib statically had to provide a new build (or include the fix in their next release). There have to be thousands of applications out there who weren't upgraded (old version, vendor out of business, whatever) and who are vulnerable to a years-old security flaw.
That said, I ship my own software with all required dll's in one directory, too.
- mahmud 16y agoI must be too late to the party, because I have just discovered that joy that is Java and WebStart. Really, too fucking late eh?
- elblanco 16y ago> who are vulnerable to a years-old security flaw. That's an interesting point I hadn't considered. I had always operated under the assumption that DLLs were a design compromise to allow code reuse on systems with relatively constrained storage. All that being said, I still run into problems with missing or version mismatched DLLs quite frequently. It seems particularly bad with software provided by the O/S community, but there's a fair number of commercial programs where I run into these issues as well. The obvious solution to me is to just ship with all required DLLs (when possible) and install them in the local path for your app. Nobody is really going to notice another few MB missing these days.
- malkia 16y agoThis is no guarantee. There is no standard lib library/dll on Windows. Not everybody would install it in system32, and sometimes it's compiled with flags the standard distribution is not. On Linux at least people some how agreed that system version is for the better, and works there.