🚀 go-pugleaf

coolidge@cs.uiuc.edu (John Coolidge) writes:
> Depends what you mean by "The FSF approach". The copyleft is an example
> of #2. Copyleft results in a denial of "assistance"; FSF code cannot be
> used to "assist" an un'free' program (as a matter of record, I have my
> own objects with the FSF's use of 'free'). It can be argued that the FSF
> code already exists and that therefore my use of it doesn't mean they
> "assisted" me; however, I think that getting to use preexisting code
> counts, to some extent, as assistance.

I think it's a pretty odd usage of "assist".  For example, consider another
example of use of some "good" software to develop some "bad" software: the
use of existing compilers as a means of developing computer viruses.
I think if you started claiming that Microsoft assist people in developing
destructive computer viruses, people would claim that you were being
misleading.

> On the other hand, the FSF gives you the same "assistance" in
> supporting, for instance, Apple hardware. They are willing to have you
> use the code, but opt not to give active assistance. This is, I think,
> as it should be; free is most certainly not free if one must give up
> one's beliefs.

I agree.


mathew

-- 
Hail Eris! / "Our whole economy's based on fear and death; how long can we get
away with this?" --- Jello Biafra / Message for Kodak: Bring back Dan Bredy! /
PGP RSA public key available on request / Desperately seeking Negativland's U2
CD / Just another would-be Mac owner put off by Apple's monopolistic practices