Have you considered using a less-easy-to-read format like asm.js, run a obfuscator over the source, or put your IP into a binary node module?
--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups "v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Maaf saya tidak kesengajaan saya. T.ksh
As pointed out by others, there are de-obfuscators available; we want something more robust than that.
The whole reason for introducing node.js is to benefit from the resulting productivity - at least in our company programmers are loving javascript more than C/C++ - happy programmers are productive programmers.
Thanks for your thoughts.
This is an enterprise application given in the form of an installer. We are not doing SaaS.
Many thanks for the ideas guys. We want this to be a generic solution, not one particular js tied up within a custom binary. The idea is to have the source files present on disk as encrypted files. This allows us to easily roll out new patches, add functionality
by adding new files, etc. Having a separate executable for each independent bit of javascript would become unmaintainable very quickly.