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 to write a little system to do a particular job (As much an experiment to see if these new "desktop computers" were useful tools or just cute toys as for the actual outcome.) It was clearly applicable to other branches, so I made it appropriately generalisable from the start. Some of the other ministries contracted me to adapt the government-owned code for them. I had a lot less cleaning up to do where they said "Please install it for us" than when managers had hijacked the code and tried to implement it as their own creation. On 10/23/17, Shlomi Fish <shlo...@shlomifish.org> wrote: > Hi Mark, > > On Sun, 22 Oct 2017 22:37:31 +0000 > Mark Devine <m...@markdevine.com> 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 adoption. >> Then >> there’s the commercial side, which would also drive the language from >> another >> important angle. I believe in a balance of public sharing and private >> enterprise. >> >> I am interested in packaging some of my long-term Perl 6 >> projects/scripts/apps/frameworks into some kind of relocatable object >> form >> (binary) that cannot be easily altered or trivially reverse engineered. >> Put >> another way, I sometimes would prefer not to sell source code to my >> customers, but rather some form of compiled package that can’t easily be >> diddled by a SysAdmin. If I create code for a particular commercial >> domain >> over years, then I want to get compensated for it and not have it be >> diluted >> with copy-cats one week after I release it. Certainly some of the >> generic >> libraries that I create in the future can be modularized for the Perl 6 >> ecosystem and I’ll push those eventually, but the really specialized >> domain-specific code that fills a commercial void & that I will commit >> years >> to maintaining, I’d like to offer a commercial license, key-protect, sell >> subscriptions, etc. >> >> Again, I’m very interested in contributing to the ecosystem when possible. >> I >> still need to grow past baby/teenager Perl 6, and I’ll get there soon. >> But >> after creating something targeted only for customer >> purchase/subscription, >> what tools are available in the Perl 6 toolbox? I saw something for the >> Java >> back-end (to .jar), but not much else. >> >> Is there a Perl 6 roadmap that might mention compiling Perl 6 >> modules/scripts >> into something atomic, binary, & relocatable? Or preferably the >> capability >> to compile only specific Perl 6 modules, requiring an existing Perl 6 on >> the >> target host? >> > > Please see > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ.mdwn#how-do-i-hideobscureencrypt-my-source-code-to-prevent-end-users-from-learning-how-it-works > . > > Regarding "Intellectual Property", see > https://www.linux.com/news/why-term-intellectual-property-seductive-mirage > and > http://ericsink.com/articles/Intellectual_Property.html . > > -- > ----------------------------------------------------------------- > Shlomi Fish http://www.shlomifish.org/ > Best Introductory Programming Language - http://shlom.in/intro-lang > > I’m worser at superlatives. > And I don’t ever use no double negatives. > — James at War, “Bad Grammar”: > http://www.youtube.com/watch?v=Mj6QqCH7g0Q > > Please reply to list if it's a mailing list post - http://shlom.in/reply . >
