Linked by Andrew Youll on Tue 19th Jul 2005 15:57 UTC
Permalink for comment 6350
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



Member since:
2005-07-06
If there's a bug in a library, not only one package needs to be fixed, but dozens.
Dozens is probably an overstatement, but it is a valid observation. However, look at it this way - I'd rather replace ten copies of a library (if you need to, most of the programs will work fine with the original lib) than to replace one copy of a lib and have it break ten programs.
Sometimes, updating a lib means all programs using the lib must be updated as well. By having a seperate copy for each program, you don't need to update programs which only changed because a lib changed.