Linked by Andrew Hudson on Mon 20th Jun 2011 17:19 UTC
Permalink for comment 477901
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 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2010-03-11
Have you ever worked with systems that shipped all-in-one binary packages? Most users don't like it. They constantly ask "Why is Firefox over 90MB?" "Why does it take so long to download updates?" "What about my bandwidth caps?" "How come some packages haven't addressed security concern XYZ?"
Breaking software into shared libraries and using dependency resolution greatly reduces bandwidth and vastly improves security (one library can be updated instead of every packages on the system). Yes, there are some downsides.
Every so often some developer won't test changes properly and something will break, and it means users can't just drag-n-drop an application to a new machine and expect it to work. There is a trade-off. But demanding everyone move to all-in-one bundles ignores the fact that a lot of users don't want them. Even some who think they do change their minds once they see the problems that arise.