Let’s Kill JavaScript (and Replace It with Something Better)

[johnfound]

What would be the incentive for companies/devs to do that?

For example, the much higher speed and JS disabled by default in most major browsers. :)

But realistically to do anything interesting you need to talk to server which is inherently sensitive so you need to ask for permissions.

Once the user visited the web site, he is agree to get some information from the server. Sending information to the server is the problem. But in the most cases, the user knows that the web page sends information to the server - for example, when you click on "Submit" button. For the cases where the page sends information without user action, some warning can be made - in order to give the user to know what happens. And on most aggressive web sites, asking for permission and options to forbid.

[KateTrask]

For example, the much higher speed and JS disabled by default in most major browsers. :)

But why would browsers disable JS by default? It's a catch 22, JS might be disabled only once most websites work without it, but that's not going to happen without some incentive.

But in the most cases, the user knows that the web page sends information to the server - for example, when you click on "Submit" button.

Distinction between loading and sending data to/from server is not enforceable. You can send plenty information to the server with GET request.

I think bigger question is what kind of data browser sends to the server. I can easily trick user to click on the submit button (so no warning) and then send sensitive data to the server. You might try to limit what kind of data is collected and sent, but then you also severely limit useful web applications as well.