Source Code Encryption?

[LinkUp]

I am developing an extension for my company, and they are not overjoyed with the fact that the code, since it's all in JavaScript, would be readable by anyone. Is there any way to make the source code less open? How are the people that sell their extensions commercially able to do this? Or are they just hoping that the code is not stolen?

Thanks for any info.

[old np]

The only thing you could do would be to obfuscate it, but this isn't really useful because if someone is determined to see your code, that's easy to get around.

The source isn't that special anyway. Even if you could "close source" your program, what's to stop someone from just copying it to a dozen computers?

[d~l]

Would an embedded Flash (*.swf) asset at least give a bit more protection (although there are Flash decompilers for those determined to reverse engineer the cached *.swf code). And with server side encryption added it will make it harder to crack.

[BenoitRen]

How are the people that sell their extensions commercially able to do this?

They don't.

[appoloin]

How are the people that sell their extensions commercially able to do this?

They don't.

If the extension was used to access subscription services on a server then doesn't matter if the code is copied, without a server account the extension is worthless