OO.o 2.0 compile 6637

Larry Qualig schreef:

Thought so, too. Couldn't avoid the chuckle... :-)

Ah, those were the days. My first was the MPFII with no less that 1024 bytes of RAM. Looked like an old video cbuttette box.

The term "creeping featurism, springs to mind here.

Looking at the resource usage, it's (more often than not) not the actual features that do the harm, but the eye-candy. Graphics, in particular, eat up resources like a goat munching in your cabbage patch. Then there's all the nice sounds, voices going "You've got mail" and such.

The app itself can do without them. Even with all the "extra features".

Hmmm... And how many of those features actually get used? It would be nice if you had a base app in which you can install the features you actually need, so that the user himself is in charge of the actual amount of disk-space needed. Need special feature X? Download it and install it.

In a way, this is allready customary in browsers. You can just download the plugins you want. I remember Photoshop (way back when I was developing sw for the mac) having the same functionality. So at least, it's possible.

So far, so good. But the problem remains. We buy more diskspace and the apps get even more bloated, so we buy more diskspace, etc ad nauseam. In any case, it's good for the economy, but when all's said and done, I dont have the feeling the actual functionality is imrpoving at a spectecular rate. More eye-candy, more features nobody uses, that's all the average user gets out of it.

But you're right. There's little you or me can do about it.

Nice post, btw. More of that, please.

Regards,

Kleuske.