🚀 go-pugleaf

In <1992Jan12.233119.5431@alphalpha.com> nazgul@alphalpha.com (Kee Hinckley) writes:

>In article <1992Jan10.182824.15726@sunb10.cs.uiuc.edu> epstein@cs.uiuc.edu writes:
>>Ahhh, I see now -- you want free access to whatever code you
>>want/need, but you also want to be able to restrict access to code you
>>write.  Sounds a little bit hypocritical to me.
>
>Why can't you do both?  I write commercial software for a living.  I
>take major portions of that code and post them or give them to people
>for their use where I think it would be helpful.  I don't see any
>conflict.

The example you give is a little different than what I was referring
to -- I'm not sure whether you're thinking of something different or
not.  Your example is that you sometimes let people have for free
stuff you wrote originally for proift.  My comments were about someone
wanting to have free access to code, but wanting to be able to have
more restrictive control of code they develop from that code (in other
words, no one can restrict stuff from them, but they can restrict
stuff from others).

-- 
Milt Epstein
Department of Computer Science
University of Illinois
epstein@cs.uiuc.edu