Dear Matthias,

I am first to appreciate your contribution for creating AmForth and I
sincerely don't want to even sound disrespectful but it seems to me that
you need to get educated on Open Source Licensing and the GPL in
particular.

If working with GPLv2 would have required the developer to disclose
his/her underived and independent code Linux would not have become so
popular at the core of commercial products as it is...

Just as Sam said, saving code space or feeling no guilt when using long
running words is a good enough reason.

Sincerely, Enoch.

----------------------------------------------------------------------

Sam Putman <atmanis...@gmail.com> writes:

> On Mon, Feb 17, 2014 at 8:33 AM, Matthias Trute <mtr...@web.de> wrote:
>
>> Hi Enoch,
>>
>> > I have been requested by my customer to try to make my AmForth code more
>> > difficult to "SEE".
>>
>> See below
>>
>> >  So, how do you feel about splitting the dictionary
>> > space into two segments -- one for "growing" code, one for "growing"
>> > names with the option of forgetting the latter.
>> >
>> > I must say that there is an element of Flash space saving in this
>> > suggestion too.
>> >
>> > What's your opinon?
>>
>> Won't do.
>>
>> > P/S Let's start no GPL wars here. I'm not talking about code falling
>> > under the GPLv2 license.
>>
>> You have told your customer, that amforth is GPL'ed, havn't you??
>> So if (s)he uses amforth, the source(s) of any derived work must be
>> available upon request,  There will be no battles to fight here,
>> not even a (further) discussion, GPL is accepted by many
>> courts worldwide, even in the US.
>>
>> Roma locuta causa finita.
>>
>> Matthias
>>
>
> Hi Matthias,
>
> While far from interested in code obfuscation, the ability to write
> 'headless' words would free precious Flash for more applicative code.
>
> I am concerned about part of what you appear to be implying here. Do you
> consider Forth words loaded into the AmForth environment to constitute
> 'derived works', and hence subject to the GPL?
>
> That would make me uncomfortable, as someone who favors the public domain
> and BSD/MIT style permissive licenses for my own work. I'm also unclear on
> what interpretation of copyright law would support this.
>
> cheers,
> -Sam.
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Reply via email to