HackerTrans
トップ新着トレンドコメント過去質問紹介求人

nikitaeverywher

no profile record

投稿

[untitled]

1 ポイント·投稿者 nikitaeverywher·先月·0 コメント

[untitled]

1 ポイント·投稿者 nikitaeverywher·2 か月前·0 コメント

[untitled]

1 ポイント·投稿者 nikitaeverywher·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 nikitaeverywher·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 nikitaeverywher·3 か月前·0 コメント

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

5 ポイント·投稿者 nikitaeverywher·6 か月前·2 コメント

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

jinna.ai
6 ポイント·投稿者 nikitaeverywher·8 か月前·0 コメント

コメント

nikitaeverywher
·先月·議論
[flagged]
nikitaeverywher
·6 か月前·議論
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
·8 か月前·議論
[dead]