3 ms·
> You chose to execute someone else's code by visiting their website. I block JS by default until I get at least a basic understanding what the site wants to d
by xg15 7y ago
> You chose to execute someone else's code by visiting their website.
I block JS by default until I get at least a basic understanding what the site wants to do. So I explicitly choose not to execute their code before I have some reason to trust the site.
> Untrue. It just so happened that the early web was a collection of static documents, and js was a hack to add some trivial functionality.
And yet every browser has a "view source" button and extensive developer tools to give users the ability to both inspect as well as change what the website is doing. Not to mention extension ecosystems that are all about tampering with website code.
> ...and hampers innovation.
Given how the web platform is still going strong after 30 years and in fact is one of the dominant and fastest-innovating software ecosystems today, it evidently didn't.
Actually, "view source" can be a driver of innovation by giving novices an easy way so see and experiment with real-world code and a way for the broader community to quickly learn from each other's mistakes: https://blog.codinghorror.com/the-power-of-view-source/ https://blog.codinghorror.com/the-power-of-view-source/
- throwGuardian 7y agoThe presence of "View Source", or extensions, or the ability to modify js is not evidence backing "All web apps need/were-meant to be open source". Just to be clear, you can pick any x86 binary and disassemble it to x86 assembly, and if you know your way around gdb, single step and view registers,etc. This is not evidence of "all programs were meant to be open source, else we'd not have disassemblers and debuggers" And lastly, how you choose to enable/disable js is of zero relevance to arguments for/against open sourcing web apps.
- afiori 7y ago> I block JS by default until I get at least a basic understanding what the site wants to do. So I explicitly choose not to execute their code before I have some reason to trust the site. But then the only difference is unobfuscated wasm vs unobfuscated javascript. In both cases an obfuscation can easily hide the scary bits anyway.