Linked by Thom Holwerda on Wed 24th Jun 2009 14:10 UTC, submitted by TuxJournal.net
Permalink for comment 370081
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/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
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
More News »
Sponsored Links



Member since:
2005-11-11
I'm slightly amused by references to bloat and obsessions with how much RAM and other resources an application uses.
I think there's 2 ways of looking at "efficiency":
1. Efficient in use. Focusing on lower requirements in order to run software.
2. Efficient development - when "bloat" occurs in order to produce software that is quicker to develop and easier to maintain, because the alternative would have meant a slower introduction of enhancements and and taking longer to fix bugs.
I think the ideal is getting the balance between those two kinds of efficiency, although obviously how well that balance has been struck is a personal opinion rather than an objective thing.
Some people seem to think that the first definition is the only one, but it really is not.
Edited 2009-06-24 18:37 UTC