7 ms·
> The only one I know of is that you have to go to about:config to disable Javascript. And I frankly don't see any problem with that. The modern Web requires
by duskwuff 8y ago
> The only one I know of is that you have to go to about:config to disable Javascript.
And I frankly don't see any problem with that.
The modern Web requires Javascript. Most major web sites will fail to work properly without it, often in confusing ways. (For example, Youtube will just display as a bunch of gray boxes.) Hiding a setting whose effect, for most users, is effectively to "break" the browser, is entirely appropriate.
- snazz 8y agoPeople who are genuinely serious about blocking JavaScript (like me, and I’m sure many others in the HN crowd) are happy to install NoScript, especially since it gives you much more fine-grained control than simply on/off. I agree that hiding it behind an about:config switch is perfectly fine, considering that there is rarely a legitimate reason to use the setting.
- Nicksil 8y ago> The modern Web requires Javascript. I disagree. There is nothing about the "modern" web which necessitates the use of JavaScript. I can understand the argument that, due to JavaScript's ubiquity, interfacing with some websites may prove impossible. But even then, that shortcoming isn't anything to do with the "modern" web; developers simply chose not to engineer a system capable of gracefully degrading.
- jscholes 8y ago> > The modern Web requires Javascript. > I disagree. The argument was not that the modern web requires devs to over-rely on JavaScript, forsaking all others and creating experiences which fail to function without it. The argument was that for the majority of users to interact with the majority of modern websites, JavaScript is required to be turned on. Which it is.
- Nicksil 8y agoI understood and addressed the argument in my initial reply. > ... for the majority of users to interact with the majority of modern websites, JavaScript is required to be turned on. This is a self-inflicted wound.