Re: Source code (was: The Wilkes-Barre fiasco...)

["Mike Naughton" <mnaughton@xxxxxxxxxxxx>]

Or, in fairness, because a third party could take a peek and find some
actually pretty clever coding methods and techniques and incorporate them
into their own code, which they would then sell for a cheaper price
without bothering to give credit.

I'm not really taking sides in this discussion (I've been on both sides)
-- just pointing out that a world where everyone is out to cheat you is a
world where _everyone_ is out to cheat you. IMHO, the world that each of
us actually lives in is -- by no means completely, but to some degree -- a
matter of personal choice. . . .

James Kilgore writes:
>Buck,
>
>It's widely believed to be a poor business decision because the business
>making
>that decision can not hold the code for ransom or charge outrageous fees
>for
>trivial upgrades or have a third party take a peek at what a piece of
>cra* the
>system might actually be.
>
>Buck Calabro wrote:
>>
>
>> I work for a software vendor, and it's widely believed that giving the
>> source code to the customer is a poor business decision.  Our code is
>indeed
>> in escrow, as is the Cool:2E (Synon) model that it was generated from.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com