|No such thing as a small change|
Re: Why is it bad to hide the source?by daveola (Acolyte)
|on Oct 26, 2010 at 20:06 UTC||Need Help??|
This post is very one-sided. For example:
> "I live by programming. .. ask money for e. g. bugfixing?"
Okay, but there are *other* reasons besides bugfixing, like attempting to limit distribution of code, which is pretty difficult if the source is open. You cleverly ignore the rest of the discussion by framing the question and answer.
And I *know* that any such hiding or copy protection scheme can be hacked by a talented and motivated hacker, and yet I still lock the door to my house, and I bet you do as well, even though locks can be picked.
Really what this comes down to is that some people don't believe in obfuscating source for ethical reasons (i.e., the Open Source movement) and so they push for others to not attempt to hide their source for practical reasons (i.e., the superhacker argument). We do not live in a society of superhackers. And even if one superhacker finds a way to hack your code and distribute it does not mean that everyone in the world will start using it for free (unless we're talking about music ;-)
It seems to me that this is clear:
There are very strong ethical considerations for whether your source code should be hidden or not. It might be worth reading some of the arguments for both sides, you may find yourself an open source convert.
And if not, then you'll have to be wary of all the converts trying to give you technical advice with an ethical slant behind it.
There *are* "solutions" for packaging your perl code, all with different tradeoffs and costs. If you are looking for something free that works with plenty of simple scripts, then consider:
(Written because I needed exactly such a solution myself, even though most of my perl code is completely available as source!)