home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!jhunix.hcf.jhu.edu!blaze.cs.jhu.edu!jyusenkyou!arromdee
- From: arromdee@jyusenkyou.cs.jhu.edu (Ken Arromdee)
- Newsgroups: gnu.misc.discuss
- Subject: Re: "official" FSF position on apple
- Message-ID: <1992Sep15.214339.8015@blaze.cs.jhu.edu>
- Date: 15 Sep 92 21:43:39 GMT
- References: <ROSSINI.92Sep15102354@biosun4.harvard.edu> <1992Sep15.185227.2692@blaze.cs.jhu.edu> <1992Sep15.194156.25683@murdoch.acc.Virginia.EDU>
- Sender: news@blaze.cs.jhu.edu (Usenet news system)
- Organization: Johns Hopkins University CS Dept.
- Lines: 21
-
- In article <1992Sep15.194156.25683@murdoch.acc.Virginia.EDU> gsh7w@fermi.clas.Virginia.EDU (Greg Hennessy) writes:
- >#Why _does_ the FSF allow its software to be ported to Apple machines, even if
- >#it refuses to do so itself?
- >Because restricing the distribution of code is what the FSF is
- >fighting for.
- >Because the FSF is one of the few organizations that still recognize
- >the difference between forbidding someone from doing something, and
- >not helping somebody do something.
-
- What it means to "help" someone is extremely fuzzy.
-
- If I can take a year to write a compiler for a Mac, or I can take a month
- to port GCC to the Mac, I'd argue that FSF is "helping" me get a compiler
- for the Mac.
- --
- "the bogosity in a field equals the bogosity imported from related areas, plus
- the bogosity generated internally, minus the bogosity expelled or otherwise
- disposed of." -- K. Eric Drexler
-
- Ken Arromdee (UUCP: ....!jhunix!arromdee; BITNET: arromdee@jhuvm;
- INTERNET: arromdee@jyusenkyou.cs.jhu.edu)
-