On Tue, Mar 9, 2010 at 10:09 PM, Walton H.
so please inform me.
extract the code. Of course even technologies built on Java or .NET are
fairly easy to reverse with a little knowledge (Or written in C for that
matter). I guess the real question is why in the world would you
release your code to a rival? Suffice it to say, if you have someone
actively trying to steal your code, there is no programming language
that will stop them. There are tools that can help make it more
difficult, but it’s always possible by someone sufficiently knowledgeable.
The question of obfuscating code comes up a lot here. One of the more
reasonable desires for it is to stop a client tinkering with it, or
control how it is updated with respect to support etc. I am sure python,
perl,Tcl mailing lists are full of this too.
Generally people are happy with packaging solutions, where the source is
not sitting on the file system and so cannot be tinkered with and
easily. JRuby offers a few options here with Rawr possibly, and Warbler
you to create self contained Rails apps that are indistinguishable from
java WAR files. Crate is another packaging solution that I have heard of
may be useful.
Once you are distributing your code, these options will only hide your
from casual snooping. A determined individual will be able to unpackage
application, inspect the code and repackage it. Signing the package may
provide some options to help you control this problem, but it wont hide
As to why Ruby source is being singled out in this case I don’t know.
if your employer takes a hard line on this, my sympathies. My experience
is that naive false assumptions on how ‘protected’ the source is by
can only rarely be undone. Its usually an emotive problem.