From: Paul Keinanen on
On Sun, 07 Mar 2010 20:10:22 -0800, Jon Kirwan
<jonk(a)infinitefactors.org> wrote:

>
>"Modest," for me, is 512 flash and 16 RAM. "Small" would be
>half that. "Decent" and kind of roomy is anything like 4k
>flash and 512 RAM. "Unbelievably big" is 40k flash and 4k
>RAM.

With such limited amount of memory, why would one need (L)GPLed code ?
If one understands what he/she is doing, why would you want to use
code written by someone else ?

Algorithms have been published in Fortran, Algol, Pascal and most
recently in C. Software patents (e.g. generating a graphical cross
hair cursor by XORing) are a hot debate issue in some countries, but
in most countries, this should not be a general issue.

Regarding the ability for the end user to replace the library code in
LGPL, why not simply put a jump table at the start of each EPROM as
was done 30 years ago, so that library code could be recompiled,
relinked and reburned individually (in those days burning a 1-8 KiB
EPROM took at least 5 minutes), in order to continue tests the same
day.

From: Paul Keinanen on
On Mon, 08 Mar 2010 10:20:46 -0700, D Yuniskis
<not.going.to.be(a)seen.com> wrote:

>> How about "Written by Jon Kirwan 2010. This file is hereby released into
>> the public domain" ?
>
>You might want to be careful about using that phrase! Not only
>does it's meaning vary from country to country, but it essentially
>says, "You can behave as if this was *your* original work
>without giving *me* any credit/mention".

If you want to donate something to the public domain (e.g. since you
notice, it would be impractical to collect any revenues), why not say
so ?

Of course, you should include statements like "AS IS" in order to
avoid legal consequences if some idiot uses your buggy code without
checking and kills thousands of people :-).

From: D Yuniskis on
Hi Paul,

Paul Keinanen wrote:
> On Mon, 08 Mar 2010 10:20:46 -0700, D Yuniskis
> <not.going.to.be(a)seen.com> wrote:
>
>>> How about "Written by Jon Kirwan 2010. This file is hereby released into
>>> the public domain" ?
>> You might want to be careful about using that phrase! Not only
>> does it's meaning vary from country to country, but it essentially
>> says, "You can behave as if this was *your* original work
>> without giving *me* any credit/mention".
>
> If you want to donate something to the public domain (e.g. since you
> notice, it would be impractical to collect any revenues), why not say
> so ?

The point is that you need to understand what this *really* means.
I.e., you can;t change your mind later. OTOH, with a license,
you *can* change the terms of your license and the folks who
fall under those terms.

You will note very *few* things are deliberately placed into
the public domain -- despite license terms that effectively let
you do *anything* (except claim it as an original work) with it.

> Of course, you should include statements like "AS IS" in order to
> avoid legal consequences if some idiot uses your buggy code without
> checking and kills thousands of people :-).

IANAL so I'm not sure what the actual legal liability is
for things like this.
From: Oliver Betz on
whygee <yg(a)yg.yg> wrote:

[...]

>seems so, nice code, but please, if you can,
>put the files in a subdirectory so there is no need
>to sort them after they are uncompressed in a crowded directory :-)

that's a matter of taste. I decompress explicitly to a new directory,
so I prefer archives without another subdirectory.

Oliver
--
Oliver Betz, Munich
despammed.com might be broken, use Reply-To:
From: Jon Kirwan on
On Tue, 09 Mar 2010 08:48:12 +0100, Oliver Betz
<obetz(a)despammed.com> wrote:

>whygee <yg(a)yg.yg> wrote:
>
>[...]
>
>>seems so, nice code, but please, if you can,
>>put the files in a subdirectory so there is no need
>>to sort them after they are uncompressed in a crowded directory :-)
>
>that's a matter of taste. I decompress explicitly to a new directory,
>so I prefer archives without another subdirectory.
>
>Oliver

That's the way I do it, as well. Which is why I set it up
the way I do. Also, WinXP (which I am using here) appears to
automatically want to create a directory by the same name as
the zip -- if one doesn't edit the default. Adding another
directory in the zip would compound that problem, too.

It's hard to do a one-size fits all here, I suppose.

Jon