Slashdot Mirror
All Hail Bloatware
Zarn writes "In Tuesday's Slate edition Andrew Shuman, in his
article The Love Bloat, argues that the problem with bloated software is that it isn't bloated enough and that we, the customers,
are the ones demanding bloat! " Heh. I'm wiping a tear off of my check from laughing so hard - Jonathan Swift, here we come.
muLinux is probably the most versatile and interesting one-floppy-disk distribution of Linux out there. (Mr.) Michele Andreoli has written some incredible apps, such as an http server that's less than 1500 bytes in size. You can get X-windows on a second floppy, too. If you want it all (gcc compiler, ssh...), you'll have three floppies to deal with. I've been having lots of fun with this package...and very little bloat.
Check it out at www.sunsite.auc.dk/mulinux
Certified Microsoft Notworking Specialist
I don't buy that bloat is caused solely (or even *predominantly*) by user-requested (user-wanted as per market study) features.
For instance, who the heck asked for that damn paper clip and his moronic friends!!?? Who thought to themselves: "Damn it! I can't do a thing with this Office97...hey! I know! A dancing paper clip would really help me a lot!"
Also...Users don't buy upgrades JUST for new features. In fact, I'd argue users buy upgrades JUST so that they can stay current enough to work with everyone (and everything) else. Maybe if Microsoft didn't break its old file formats and introduce new ones every rev then people wouldn't upgrade as much. I got Word 6.1 for free with a new computer and have to date not installed a new one. I can't use documents from work though (and NO, it was not my choice to use MS Office...).
In the same vein, I think embedding HTML functionality into everything is stupid. I hate getting those bloat laden HTML messages from people in Pine, which I have to decipher for myself. Sometimes these messages include two attachments: one HTML attachment for bloated email readers, and one plain text attachment for normal ISO8859_1 readers. Over double the bandwandth of the simple plain text message. Most people don't even know this feature is on when they sprinkle bold, italic, and font tags all through there 1 line message and 6 line sig.
Bloat is also caused by laziness. I guess nobody at Microsoft ever thought "Hey, if we actually took the 3 extra months to get this really tight we might have a product consumers would buy and not feel like it was being stuffed down their throat." The lazy approach to complexity is to just scale up the same techniques and practices you were doing before. It's easy to copy your O(2^n) parser from Bloatv1.0 to Bloatv2.0 to use with files 10 times bigger. It's harder to redesign the whole architecture.
In any case, it seems to me the bloat coming out of MS is more due to two things: 1) Introducing useless technologies and additions to 2) Position themselves strategically for even more dominance,
than attempting to add things users *want*. Heck, I've *wanted* a smaller, tighter office suite for years...they haven't added *that* feature.
It's 10 PM. Do you know if you're un-American?
Well, not always -- he does talk about the elegance of Windows [shudder] -- but his basic point is valid: people like to have features not necessarily to use them. IMHO bloat is caused by:
...
(1) One-program-does-it-all philosophy, which by, the way, is a valid design viewpoint. Emacs belongs to this school of thought, while Unix takes the opposite extreme (plenty of small interacting programs).
(2) Monolithic design, which is NOT a feature. MS Word has features targeted at lawyers (and useless for everybody else), at accountants, at writers, etc., etc. You don't need most of them, but get all of them anyway. Pluggable modules would have been a much cleaner solution (you are a lawyer? plug in the "Lawyer" module...)
(3) Feature competition between programs, which is driven by users: "What, your program cannot do a mail-merge to an index which includes animated GIFs and print out each third line?? It sucks, mine can do it!".
(4) The need for backward compatibilitly. This is less visible in application programs and more visible in system tools which often must be bug-for-bug compatible with everything going back ten years or more.
(5) The need to support all hardware under the sun. And the number of cool devices that you can plug into a computer grows and grows and grows and
(6) In the trade-off between a clean/tight code and speed of development, speed almost always wins. In the current business environment projects that are 50% over budget and on time are much much better than projects that are on budget but 50% late. Basically, the slogan is: "who cares whether it is optimized, if it works, ship it!" (in case of MS or games it is often "who cares if it works properly, ship it anyway!")
So I don't believe it is the malice of Microsoft or the incompetence of programmers that gives us bloated programs. Basically the definition of a bloat is "this program demands more resources than I expected it to". Having more resources available is a (not necessarily the) solution. Yes, Office 2000 needs ~200Mb of disk space to install. So what? I recently bought myself another hard drive -- it cost under $200 and is 10Gb in size. Do I care that much about allocating 2% of it to MS Office? Guess.
Bloat is bad in that it adds complexity which is the enemy. Insofar it consumes computer resources it is tolerable.
Kaa
Kaa
Kaa's Law: In any sufficiently large group of people most are idiots.