Browsers need to move from tens of fine-grained permission requests, to "Do you want to install this web app and give it full access to your computer?".
And from there, they need to stop building abstractions such as WebSocket, IndexedDB etc. and start exposing raw OS capabilities such as UDP, TCP and FS. Basically packaging node.js would do the trick here.
Also see Tim Berners-Lee in "Installing web apps":
"If I can't give power to apps, then the web app platform cannot compete with native apps."
He asks for something fine-grained but the main point is to expose the real power of a machine to an app if the user so wishes. That's not possible today with browsers.
Browsers need to stop controlling innovation, and push core services out to the edges and let innovation happen there. Stop drafting specs for WebRTC etc. and give UDP etc. back to the people.
If the browsers don't do it, maybe someone will make a new kind of browser that will with something like Electron.
And from there, they need to stop building abstractions such as WebSocket, IndexedDB etc. and start exposing raw OS capabilities such as UDP, TCP and FS. Basically packaging node.js would do the trick here.
Also see Tim Berners-Lee in "Installing web apps":
"If I can't give power to apps, then the web app platform cannot compete with native apps."
https://lists.w3.org/Archives/Public/public-webapps/2012JanM...
He asks for something fine-grained but the main point is to expose the real power of a machine to an app if the user so wishes. That's not possible today with browsers.
Browsers need to stop controlling innovation, and push core services out to the edges and let innovation happen there. Stop drafting specs for WebRTC etc. and give UDP etc. back to the people.
If the browsers don't do it, maybe someone will make a new kind of browser that will with something like Electron.