bloatware

This point kind of got lost in the IP scuffle.

There are many definitions of bloatware.  For some it is installation add-ons
and data files.  For me it is sheer text segment program code.  The other
forms are easy to trim, but code is hard to rework to make more efficient.

"Why is this a problem?  Don't people need lots of features?"

Yes, but a key advantage of open source is user control.  Having the source
supposedly gives the user more control of the software.  And when the code
base bloats beyond a certain point of diminishing returns it becomes so
difficult that the user loses control anyway, and the advantage is lost.

It also becomes increasingly difficult to maintain, which raises questions 
about future sustainability.

"Oh, fine.  And I suppose you are going to correct this, Professor?"

Ha, ha.  But for myself, maybe, if I have the time.  I've found some
approaches and keep looking for more.  But it's reached the point where it
won't be solved overnight, otherwise it wouldn't be a problem.

Maybe eventually I'll come up with something that will inspire someone else. 
Or someone else will.  Or it may turn out to be one more incurable
lemming-like feature of human nature and existence, and open source may prove
meaningless.

After writing the above, I looked out on this sunny morning and saw a couple
of birds eating seeds on my patio.  Those are the dinosaurs.  Small is
beautiful.


-- Jim Howard  <[email protected]>