Article View: gnu.misc.discuss
Article #73308Re: Wanted: blurb supporting GNU integrity
From: Jesse Perry
Date: Tue, 15 Oct 1991 14:30
Date: Tue, 15 Oct 1991 14:30
66 lines
3519 bytes
3519 bytes
mathew@mantis.co.uk writes:
>
> There is, therefore, some merit to the argument that with
> commercial software you can demand a certain amount of support
> from the supplier which you can't demand with free software or
> GNU software.
It's true that you can't "demand" support of GNU software. But
it's also true that you don't have to: GNU software is supported.
Contrast this with the commercial environment where, in my
experience, if the vendor isn't willing or able to provide
support, you are out of luck no matter how loud your demands
may be.
For example, we (Franklin) used to report an occasional bug in
Sun's cc. We even provided small (10-15 line) example programs
which exercised the bugs. I can't recall *ever* getting a fix
for *any* of them. Eventually we quit trying. I doubt things
have improved in the ensuing year or two, since Sun now sell
an ANSI C compiler, and therefore have even less incentive to
fix the one they provide free.
(Aside: why would anyone buy Sun's new C compiler, when they
couldn't manage to get their old one right even after at least
ten years of working on it?)
If I find a problem in GNU C, I have several options for
support:
o Wait for the next update -- it may already be available.
GNU software is updated regularly.
o Post a message on the net. Odds are, other people have
seen this problem, and already have a patch to fix it.
This doesn't work with commercial products, because
you don't have their source available to patch.
o Send mail directly to Richard Stallman. Although he's
a busy guy (I'm told -- I've never met him) he remains
directly involved in gcc development: see the gcc-1.39
ChangeLog file. This kind of personal accountability,
for GNU software, or for any other product, makes for
much more responsive support than can be expected from
the anonymous "support department" of FooBar Corp, let
alone an outfit as large as Sun.
o Dig through the source myself to find the problem, since
the source is available. I don't recommend this as the
first thing to try, because it takes time away from
productive work. But if you run into a must-fix bug
that won't wait, it's nice to be *able* to do this.
o Buy support from Cygnus, -- since support is their main
line of work, one can expect them to be at least competent
at it. Disclaimer: I have no connection with Cygnus
Support, and have never used their services, *because I
haven't needed to* -- the other support options have been
more than adequate for my needs.
In short, I find GNU software *much* better supported than
many commercial packages. For me, this is actually a better
reason to use GNU stuff than the fact that it's costless.
Jesse Perry jesse@franklin.com uunet!frnkmth!jesse
Technical Details
Message-ID:
<1991Oct15.143034.2239@franklin.com>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!usc!elroy.jpl.nasa.gov!decwrl!twwells!frnkmth!jesseReferences:
<RSW.91Oct13024138@delay.cs.brown.EDU> <cycT021w164w@mantis.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,d88347b61bea92a1 X-Google-Attributes: gid1025b4,public X-Google-ArrivalTime: 1991-10-16 10:57:54 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!usc!elroy.jpl.nasa.gov!decwrl!twwells!frnkmth!jesse From: jesse@franklin.com (Jesse Perry) Newsgroups: gnu.misc.discuss Subject: Re: Wanted: blurb supporting GNU integrity Message-ID: <1991Oct15.143034.2239@franklin.com> Date: 15 Oct 91 14:30:34 GMT References: <RSW.91Oct13024138@delay.cs.brown.EDU> <cycT021w164w@mantis.co.uk> Organization: Franklin Electronic Publishers, Inc. Lines: 66