Your latest post seems to me far more appropriate to the very intelligent person 
that you are.  Seeing that you develop closed apps 9-5, you must therefore understand
that is sometimes necesary in order to feed your family.
As someone else noted, not all of us can mak a living from the royalties of on book,
like Larry has managed to do.
Myself, I write open source code 40 hours per week and make my living doing installation
and configuration of my software.  In the 13 years I've been coding, I've 
written precisely 3 proprietary apps.
The other hundereds of programs have been open source, even little utility programs
like this obfuscater that I write for my own use - as soon as I wrote it I
found a place to post the source for others to use.
I was then criticized for making my obfuscater available to you and others.

2 of the 3 programs that I have kept proprietary have been implementations of
new security methodologies that I have developed.  Given the precise nature 
of these two specific programs their utility is greatly enhanced by making
their operation non-obvious.  (That may not apply to a lot of security schemes, 
but in these two specific cases it's true.)
Both have also been methodologies that I have spent months developing and must
be paid for if I'm to pay my rent.  Specically, this script I'm obfuscating now
has taken me close to a year to develop. During that time my rent has gotten 3 
months past due.  If I'm to be around to develop anything, I have to have
users of this software pay for it.  That's reality.
These scripts are designed to let a company protect their confidential data.
If they want to save thousands or millions by using my software, I think 
it's reasonable to expect them to pony up $50 to help cover the cost of development.
It's also a fact that other companies have attempted to steal both of my
security technologies while my products were still in beta.
That's not a theory - that's hard reality for me.
My family is about to be homeless while some jerk is making big money stealing
my technology that I spent a year developing.
I don't intend to make that any easier than necesary.
It would be nice if everyone were trustworthy, but that's not reality.

So while you are taking a break from your full time job developing proprietary
software please don't spend that precious time criticizing me for giving away
my obfuscater.  I would perhaps be more receptive to your ideas of you actually
helped someone else by suggesting ways to obfuscate that one line, but if 
you are only here to stroke your own ego and show off then please share
your thoughts with your fellow full time proprietary coders around the office 
and not bother those of us who eek out a living giving our work away.

Ray

In reply to Re: Re^3: An obfuscation script, and a question by Anonymous Monk
in thread An obfuscation script, and a question by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.