Please reply to list if it's a mailing list post - http://shlom.in/reply .
Begin forwarded message:
Date: Thu, 26 Oct 2017 07:43:43 -0700
From: James Ellis Osborne III <jamesel...@twee.se>
To: Shlomi Fish <shlo...@shlomifish.org>
Subject: Re: Perl 6: Protecting Intellect
On Mon, 23 Oct 2017 10:57:20 -0700
James Ellis Osborne III wrote:
> This particular app was .pyd files locked with calls to a C dll. Source
> code is reconstructable but for an app of more than a few thousand lines
> it's highly unlikely anyone is going to go rebuilding it
Hi James,
On Mon, 23 Oct 2017 07:19:34 -0700
James Ellis Osborne III wrote:
> Is compilation to bytecode still a todo feature? I managed to get a
> solution supporting compilation, serial-based locking, & license expiration
> delivered in Python last month for the nuclear
Frankly, if you're worried about this sort of thing, you have too much
faith in "secret sauces", and not enough in understanding situations
thoroughly. Code is trivial, implementation isn't.
Back in the days of dBase II, I was a contractor for one ministry of
the local government. They asked me
Hi Mark,
On Sun, 22 Oct 2017 22:37:31 +
Mark Devine wrote:
> Perl 6 Users,
>
> [[ Bouncing off Re: who own my code? ]]
>
> This is the first of several possible spin-off questions, but here goes…
>
> Perl 6 has its public ecosystem, which will drive growth and
Perl 6 Users,
[[ Bouncing off Re: who own my code? ]]
This is the first of several possible spin-off questions, but here goes…
Perl 6 has its public ecosystem, which will drive growth and adoption. Then
there’s the commercial side, which would also drive the language from another
important