Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!nuchat!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.misc Subject: Re: Borland and other proprietary bloodsuckers (Was: Re: BISON, GCC, and the GNU public license.) Message-ID: <5559@ficc.uu.net> Date: 6 Aug 89 14:11:23 GMT References: <26@ark1.nswc.navy.mil> <68726@yale-celray.yale.UUCP> Organization: Xenix Support, FICC Lines: 31 In article <68726@yale-celray.yale.UUCP>, Horne-Scott@cs.yale.edu (Scott Horne) writes: > In article <5486@ficc.uu.net>, peter@ficc (Peter da Silva) writes: > > In article <26880@agate.BERKELEY.EDU>, mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) writes: > > [back to commercial licenses] > > > Correct. However, I don't see any commercial license agreement that > > > doesn't require that either I buy time on the target hardware, or that > > > the owner of the target hardware buy the commercial product, if I want > > > them to have a trivial installation process. > > Check out any of Borland's products, Microsoft C, Lattice C, Lattice C++, > > Aztec C, or any of the other microcomputer compiler vendors. > I have. [long list of problems with Borland's support and buggy software] Quite irrelevant. Have a look at the subject under discussion. Has Borland ever required you to: a) Buy time on any hardware. b) Require that anyone you write code for also buy Borland products? Or, for that matter: c) Charged your royalties on your programs? -- Peter da Silva, Xenix Support, Ferranti International Controls Corporation. Business: peter@ficc.uu.net, +1 713 274 5180. | "The sentence I am now Personal: peter@sugar.hackercorp.com. `-_-' | writing is the sentence Quote: Have you hugged your wolf today? 'U` | you are now reading"