HackerTrans
TopNewTrendsCommentsPastAskShowJobs

nikitaeverywher

no profile record

Submissions

[untitled]

1 points·by nikitaeverywher·mês passado·0 comments

[untitled]

1 points·by nikitaeverywher·há 2 meses·0 comments

[untitled]

1 points·by nikitaeverywher·há 3 meses·0 comments

[untitled]

1 points·by nikitaeverywher·há 3 meses·0 comments

[untitled]

1 points·by nikitaeverywher·há 3 meses·0 comments

Ask HN: Do you protect your client-side JavaScript? Why or why not?

5 points·by nikitaeverywher·há 6 meses·2 comments

Show HN: AI Invoicing with Jinna – Create, Send and Chase to Get Paid Faster

jinna.ai
6 points·by nikitaeverywher·há 8 meses·0 comments

comments

nikitaeverywher
·mês passado·discuss
[flagged]
nikitaeverywher
·há 6 meses·discuss
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?
nikitaeverywher
·há 8 meses·discuss
[dead]