Food for thought: I think the author is right. I was considering his article and tried to think of some signs that you could tell your software has turned to bloatware. So far I can only think of one:

1. When your program team cannot account for what is going on in their responsible areas.

If there is only one programmer, he should know what is going on in whatever part of his program. If it is a design team, then each person's respective section.

I say this because if you cannot account for what your code is doing where, you have a problem. Auditing is important.

That being said, I am starting to feel like all software in general, not just Microsoft software, is headed towards the "bloatware oblivion" point.

However, with some projects concentrating on features to please their customers, coupled with the many other focuses and goals that projects can have like security and such, I'm wondering if it's reasonable to expect them to also focus on trimming down the code.

But I tend to believe that Microsoft has no intention of doing this because of signs which seem to point to Microsoft Windows driving the "I need a fast computer" craze (and more so, gaming, but that's a different issue).

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/300/30670#30670