On 04/03/13 17:35, Harald Kirschner wrote: > As David said, obfuscates would be a first step to protecting your > code. UglifyJS already munges several special cases for more > efficient code, making it harder to reverse it. The next step would > be Google Closure in advanced mode, which is a one-way > transformation. > > The final and most protected path for you would be Emscripten. > Writing your business critical modules (like API client or > Encryption) in C++ and compiling them to JavaScript (or even > asm.js).The result resembles byte code, using typed arrays as > memory.
While some partners will no doubt do it anyway, it concerns me a little that we are going around actively recommending these things. Mozilla runs the Webmaker program, whose entire point is that the web is hackable and remixable, and that people should do that. It's this ability to change and innovate which is part of the selling point of Firefox OS to users and carriers. If every Firefox OS app came as a bit of Emscripten-compiled-from-C++, then it would be a very sad day for the open web. Gerv _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
