From:	nelson AT cs DOT uwp DOT edu (Jeremy Nelson)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GRX v2.0 Font(s) Distribution (.FNT files) and Copyright text
Date:	15 Feb 1997 02:32:32 GMT
Organization:	University of Wisconsin - Parkside
Lines:	42
Message-ID:	<5e3780$ll1$1@news.inc.net>
References:	<5e2jgr$59v AT news DOT interlog DOT com>
NNTP-Posting-Host:	cs.uwp.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Gautam N. Lad <gautam AT interlog DOT com> wrote:
>Although my programs are freeware, the source is not (and never will be) 
>available.  Why?  I don't know, it's just that I put my self through a lot 
>when making programs, and I don't want to waste my energy for others.  Unless, 
>I change my mind.  [...] Unless what you're telling me is SERIOUS!

I just have a comment on this issue:  It seems that you are open to
comments about this point.

I understand why you dont want to release source code to your programs,
and have been through the arguments myself (someone else will rip off
my code and use it in another program, and i wont get money off of it,...)
When you look at the big picture, most free software programs are small
in nature (in the grand scheme of thing, 1 meg of source is pretty small)
and that the code you have written may contain something clever that someone
may be able to put to good use to make their program better than otherwise.

Directly, releasing source code benefits you, as a developer, because the
c-literate users of your software will surely find the bugs in your program
(all software has bugs), and when they have the source code available, they
are able to fix the bugs, and send the patches back to you.  This may sound
hokey, but it really does work.  People who fix bugs in software that they
genuinely find useful get a real kick out of being able to help make the
product better, and the developer saves time in debugging, since there are
many more eyes on your code looking to fix bugs...

Indirectly, anyone who might "rip off" your code, or parts of it and include
them into your program would only do so because either they could not do
it better, or your solution was sufficiently insightful so as to present a
truly unique solution to a problem.  In either one of these cases, the
inclusion of your code into other's software, with or without you recieving
compentation for it lends to the greater benefit of the software base --
someone else's software is better for all of us, because you were willing
to share your property.


I dont neccesarily expect you to change your mind, as it is ultimately
a personal decision that many people feel very sensitive about.  However,
i do just hope to make you think about the plusses that you get from
allowing others to have access to your source code.

Jeremy Nelson

- Raw text -