> There is no such thing as a javascript binary. The code included with node > is stored in string format in the node executable.
No worries, what if the code was compiled via V8, and then stored as a data file? Whatever format it is in, if you could just load the same datafile you would'nt need the source code again. > In my opinion, this is not a Node problem to solve. Obfuscation/source code > hiding is an opportunity for a third party to make a native module to > encrypt/decrypt source files. You don't need to encrypt the source if you can just work with the intermediate data format. See above. > Most of us are standing on the shoulders of giants. This is why node is so > great. But yet, we are selling software touting features that are really a > gift from the Node community, and that we got for mostly free. I'm sorry to sound capitalistic, but sometimes you need to make commercial products for clients that are willing to pay. If my work could be protected in such a case, it would help me. And yes, nodeJS is a great gift, and I would look into giving whatever else I create back. > Bitching cause the Node creators were generous enough to share their work > with you, but not cheap enough to lock it down is ludicrous. Sorry if I sounded like I was bitching, I was just trying to make NodeJS a more professional platform: .NET, Java, Flash all allow you to 'compile' your app in some way and so I was just asking if something like this could be implemented for node. Best Regards -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" 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/nodejs?hl=en?hl=en
