Linked by Thom Holwerda on Sun 5th Nov 2006 17:40 UTC, submitted by bmeurer
Thread beginning with comment 179134
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
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
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-10-02
What kind of bloat are we talking about?

Functionality Bloat or Code Bloat. It's two different things and Functionality Bloat does not equal Code Bloat.
You can easily write an application with little functionality in a lot of code, and you can just as easily write an application with a lot of functionality in a lot less of code.
I don't mind Functionality Bloat as long as it doesn't result in Code Bloat. Code Bloat is what makes applications start slower, react slower etc.
Functionality Bloat "just" means you can't find the functionality you need - unless you search within the application for 30 minutes