I don't think there's much point in obfuscation. If it's a large amount of code then minification and concatenation helps with download size, but for small files I don't bother.
Minification and obfuscation solve different problems. Minification is about download size (and somewhat parse/exec speed). Obfuscation is about making code harder to reverse-engineer, patch or copy.
The question is: do you have anything worth protecting? For a simple marketing website, probably not. But if you're shipping:
- A browser game (think of copycats & anti-cheat front end code)
- Feature flags that reveal your roadmap
- Pricing/discount logic in product companies competitors could copy
- Client-side validation algorithms (easily explained by LLMs)
- Proprietary algorithms (trading, scoring, matching)
...then "anyone can read your source" becomes a concern.
I don't think there's much point in obfuscation. If it's a large amount of code then minification and concatenation helps with download size, but for small files I don't bother.
Thanks for the feedback.
Minification and obfuscation solve different problems. Minification is about download size (and somewhat parse/exec speed). Obfuscation is about making code harder to reverse-engineer, patch or copy.
The question is: do you have anything worth protecting? For a simple marketing website, probably not. But if you're shipping:
- A browser game (think of copycats & anti-cheat front end code) - Feature flags that reveal your roadmap - Pricing/discount logic in product companies competitors could copy - Client-side validation algorithms (easily explained by LLMs) - Proprietary algorithms (trading, scoring, matching)
...then "anyone can read your source" becomes a concern.
Does any of that apply to what you build?
[dead]