On Tue, 8 Aug 2000, Karl J. Runge wrote:
> So the rapid feature bloat we see is OK but compatibility bloat isn't?
>
> Here's a proposal: let's recycle 3% of the feature bloat and reserve
> it for compatibility bloat. ;-)
If you're providing features that are desireable and which people are
using, is it in fact bloat? I'd have to say no... Large doesn't
necessarily mean bloated. I generally reserver the word bloat to be used
in the context of "undesireable" -- A 300 lb. body builder is very large,
but generally you would not use the term bloated to describe one.
One of the great things about Linux is (in general) if you don't want or
need something, whether it's a software package or a kernel feature or
whatever, you don't have to install it.
> a big role. But I like to think as the ratios of the above numbers
> get larger, more compatibility will be a necessity. Maybe it's a
> "life cycle" thing. We'll see how (or if) the distros handle it all.
I don't really agree with that. But it also goes with my philosophy of
"if it ain't broke, don't fix it." Just because a package has an update
available doesn't mean you MUST upgrade it. If it works fine for you,
and doesn't compromise security unacceptably, keep it. If you want to
upgrade a bunch of stuff, get the latest release of the distribution and
upgrade everything (overlooking difficulties in update procedures, which
are getting better and ought to be reasonably ironed out soon).
I'm still running RH 6.1, though 6.2 has been out for some time and 7.0 is
right around the corner. I'll hang in there until 7.1 at least, and I'll
only upgrade then if there are substantial features I want that I don't
currently have (one of which is very likely to be vastly improved 3D
rendering in X 4.x) when it comes out.
--
Derek Martin
System Administrator
Mission Critical Linux
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
