Immediately had to think about the Apple Web Store which seemed to have the same "issue" two weeks ago[0]
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.
Honestly, I think including source maps for your frontend code should be the standard. Maybe web apps will get better if people can actually start studying existing frontend sourcemaps to learn good patterns which are being used in production by companies with lots of experienced engineers. Tons of people love to complaint about terrible web apps, but finding high quality web app examples to study and learn from is actually really difficult! Let's not pretend that the trivial todo-apps are where you're gonna go to learn anything about how a real-world app is organized.
I think this title is misleading, it makes it seem like more than just the unobfuscated code has been exposed.
9 comments
[ 1.6 ms ] story [ 32.1 ms ] threadI 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...
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.
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