4 ms·
If you obfuscate client side javascript that is being served in a browser you should get banned from the internet
by peanut_worm 4y ago
If you obfuscate client side javascript that is being served in a browser you should get banned from the internet
- deleted 4y ago[deleted]
- cachvico 4y agoWhat?
- salawat 4y agoI second this proposal.
- Kiro 4y agoWhy would serving it in the browser or not matter? It's like saying all code should be open source, which is a valid opinion but I don't see why writing JavaScript and serving it in the browser would be any different. It's not like I automatically agree on making my code fully available just because I happen to target the web. Sure, you can de-obfuscate JS but you can also reverse engineer other software.
- pcthrowaway 4y agoUsers of the webpage can't determine whether they want to run the scripts from looking at the scripts if it's (well)obfuscated. Very few users may even want to do this (perhaps none), but in theory it's a nice thing that has historically been made possible by the web. Unlike binaries or backend code, the user gets the source themselves to run in their browser... fine, if you want to obfuscate it you can, but I think it's fair for users to also dislike websites that do this. I'm not talking about minifiers/bundlers which are used to make the content more user-friendly, I'm specifically talking about steps taken to make the web less accessible and less free.
- aussieshibe 4y agoI'm curious. Could you explain why you feel this way? I can understand the desire to be able to vet code that a website wants to run on your device. I don't see why that preference should create an imperative for websites to either accommodate you or be banned from the internet.