Quote: I think that when the word 'bloat' is used to often doesn't imply just an increase in size (as in size on disk or size in memory). I think it often means the 'bloat' of slower code that comes from advanced language features like virtual methods, multiple layers of interface, descriptive instead of optimized data structures, etc. That stuff does impact performance and I think it's what most people are concerned with when they talk about bloat.
References Please Bryan. Let us all know how you got to this conclusion.
If this is true, where are the groups of QA people checking out the code to ensure that the requirements of the project are met? Otherwise unchecked project creep on how many forks?
Wirth's law is quite ironic when you look at large software projects. I imagine Mame getting slower and slower when the accuracy of the project's goal becomes more realized.
Index 
Flat 
Re: Tredding on toes again
Reply
