That's totally correct, but true with anything you compile and release. Its no different than what you do with a regular Java app now ...or Flash, or C, or Objective-C, etc.
There are things you can do to obfuscate your compiled code but that too *can* be reversed. Nothing is fool proof, but providing compiled .class files beats they hell out of handing them your source code in clear text. On Oct 12, 2011, at 9:18 AM, Hassan Schroeder <[email protected]> wrote: > On Wed, Oct 12, 2011 at 1:45 AM, Brandon Black <[email protected]> > wrote: > >> JRuby has the ability to *actually compile* your ruby code into >> java .class files. > > Which, it should be pointed out, can be easily de-compiled to reveal > a pretty decent representation of your source code :-) > > The OP should note that pretty much all companies distributing their > software to end users use licensing agreements to protect proprietary > IP, not just obfuscation (via e.g. compilation). > > FWIW, > -- > Hassan Schroeder ------------------------ [email protected] > http://about.me/hassanschroeder > twitter: @hassan > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
