[Cthulhu_]

That was my reasoning as well, I used to work for a company that really wanted code to be obfuscated because they were terrified of corporate espionage. Even though the one I was working on was just a configuration interface, and the configuration was plain text files, and the application didn't do anything special, just complicated (mobile network routing / protocols, lots of domain specific knowledge but as far as I know nothing secret or difficult to reproduce with enough resources).

[saagarjha]

People are somehow really convinced their thing is uniquely special and worth stealing.

[recursive]

I think they're more often convinced that their thing is just worth stealing. There are many such things.

[crazygringo]

Exactly this.

Apps and websites get copied all the time. Somebody throws up a duplicate with ads and steals your traffic and search rankings and customers and whatever.

Adding code to prevent your product from working when it's not on the right app/domain, and obfuscating your code to obfuscate those checks, can be sadly necessary. It doesn't need to defeat a determined attacker, but just be hard enough they'll spend their time cloning something else instead.

I speak from experience...

[t-3]

Choosing to distribute your secret sauce using tools that require source to be transmitted is kind of silly if you want to keep the source secret.

[recursive]

Secret is nice to have. But in some cases publishing is the whole point.