4 ms·
Web? Yes. Browser? No. It is very convenient to have a standard API for accessing hardware over the internet. But marrying this API with browser will inevitabl
by viktorcode 6y ago
Web? Yes. Browser? No.
It is very convenient to have a standard API for accessing hardware over the internet. But marrying this API with browser will inevitably create security nightmare, as previous decades of web technologies taught us.
As a solution I would propose another API layer, between browsers and the host OS. When a browser requires access to a certain hardware capability it requests the access via this API from the OS. The OS is actually the one where this capability support is implemented and vetted, leaving browsers code much leaner than it is now.
- wintorez 6y agoI was thinking about something similar the other day. At the moment, we have 2 webs. One is for websites, and the other one is for apps that happen to run in web. I when apps run in the browser mode (with address bar, tabs, etc.), they should run in sandbox mode, but once you "install" the app (similar to add to home screen on mobile), they should be treated like a native app.
- kitsunesoba 6y agoI really like this idea, because it'd enable true per-site permissions for hardware access — currently one has to give the browser access to everything and trust its ability to restrict access as needed and keep sites cordoned off from each other. The browser itself would no longer need exceptional privileges (compared to other types of apps) in order to function as a platform.
- c22 6y agoWhen I was younger the "web" used to mean just the parts of the Internet accessed using a web browser.