🚀 go-pugleaf

In article <962@sering.cwi.nl> piet@cwi.nl (Piet Beertema) writes:
>time before they're fixed. Bugs in public domain software
>are usually fixed at an amazing speed, thanks to the whole
>community rather than a single vendor contributing to it.
>Proof of it can be found in all the bug fixes that appear
>on the news.
Psah, this is a good one. There is one other possibility: maybe
most public domain programs have a lot of bugs so they require
lots of fixes. I have taken many programs from the net to see
if they work and sometimes they do but in many cases the
software isn't reliable (especially X programs tend to
fail on our computers -- Apollo, HP835).

>A lot of software is good, a lot of software is somewhere
>between slightly broken and rightout rotten.
This is just a dumb statement: skip.

>disadvantage 1: he wouldn't get free support anymore from
>the community, which is normally crucial for public domain
>software.
If our work was dependent on public domain software we would
all be out of business. They only reason I can get my work done
is because of non-public payed-for software (that works o.k.)!


Mart van Stiphout
Eindhoven University of Technology
Dept. of Electrical Engineering -- Room EH7.34
P.O.Box 513, 5600 MB Eindhoven, The Netherlands
Email: mart@euteal.ele.tue.nl