Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uakari.primate.wisc.edu!ark1!dsill
From: dsill@relay.nswc.navy.mil (Dave Sill)
Newsgroups: comp.misc
Subject: Reasoning by analogy (was Re: Software, development & copyrights)
Message-ID: <73@ark1.nswc.navy.mil>
Date: 11 Aug 89 14:48:34 GMT
References:  <26@ark1.nswc.navy.mil> <26832@agate.BERKELEY.EDU> <5401@ficc.uu.net> <26879@agate.BERKELEY.EDU> <1312@mcrware.UUCP> <1017@anise.acc.com> <1610@bucket.UUCP>  <661@laic.
Sender: news@ark1.nswc.navy.mil
Reply-To: dsill@relay.nswc.navy.mil (Dave Sill)
Organization: Naval Surface Warfare Center, Dahlgren VA
Lines: 18
In-reply-to: darin@nova.laic.uucp (Darin Johnson)

In article <661@laic.UUCP>, darin@nova (Darin Johnson) writes:
>In article  talvola@janus.berkeley.edu (Erik Talvola) writes:
>>I don't believe this is really an accurate analogy, and I would like
>>to supply one which I feel is closer to the situation.
>> :
>But blah blah blah...

How many more analogies will be posited, debated, and refined before
we come to grips with the real problem? 

Analogies are sometimes useful for explaining unfamiliar concepts in
terms of the familiar.  But by their very nature there exists a point
at which each analogy will break down.

The *real* problem is that we don't have a good system of software
publishing; i.e., one that protects the author's "intellectual
property" and the publisher's profits without stifling creativity or
burdening the consumer.