However I agree that in the end outside of making it more readable, it's not making a huge difference.
This is front-end code, that gets deliberately sent to the browser. With enough work, someone can deobfuscate such code manually.
I think this title is misleading, it makes it seem like more than just the unobfuscated code has been exposed.
> Remember: Always disable sourcemaps in production!
Or don't. There is a non-zero possibility that this wasn't even an accident.
One has serious doubts that the person who wrote this even understands (and can articulate the reasons) why they have this position.
In any case, GitHub isn't an unredactable, append-only ledger. "Archiving" this on a site that is no less subject to DMCA takedowns than any other site but that differs from other sites in having exceptionally fast response times to takedowns is not an especially well-thought-out move.
I wish I could downvote this comment from the README.
Minification to reduce bandwidth is noble. But to obfuscate? Why?
https://htmx.org/essays/right-click-view-source/
the web is an open platform, sorry
4ggr0•2mo ago
I guess the same thing[1] applies here.
> This is not "exposing" their source code. While yes, it may not be minified and it's slightly more human readable, it's not exposing any additional logic. Remember, obfuscation is not security.
[0]https://news.ycombinator.com/item?id=45804664
[1]https://www.reddit.com/r/webdev/comments/1onnzlj/comment/nmy...