Linked by David Adams on Fri 18th Jun 2010 19:17 UTC
Permalink for comment 430760
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/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
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
More News »
Sponsored Links



Member since:
2007-11-04
Oh please ...
repeating it over and over does not make it true. Everything in a single package is a huge waste of resources:
Disk resources because you have libraries several times on your disk (and this is actually relevant if you use an SSD for example).
RAM, I'd rather use my RAM for useful things instead of keeping multiple copies of the same library in it.
Bandwidth, if a library that is part of a lot of packages needs a security upgrade, you suddenly have to download all these packages. Now let these packages be things like Photoshop and suddenly you look at multiple GB downloads. I'm not even talking about the fact that you have to wait for a new version of every one of the packages.
CPU, every app needs to check for updates, great use of resources!
Time, looking for software at places all over the internet is definitely not a better use of my time than looking in one central location.
I can't believe you actually touting all-inclusive packages as the better engineering solution.