Browser sandboxes are regularly escaped, both between same-origins and surroundings of the browser. Native apps are usually verified cryptographically, mobile a

Browser sandboxes are regularly escaped, both between same-origins and surroundings of the browser. Native apps are usually verified cryptographically, mobile almost never. Webapps shamelessly reveal many information about your usage patterns and put even your cached data at risk of being revealed to third parties. Relevance of overhead depends on what you do. Not all people restrict themselves to decoding cat videos. Browser and web-app server are additional SPOFs; and browser is unauditably complex piece of software. Cloud has storage limits, low speed, great latency and zero privacy. Moreover FSes are all about interoperability; this WebKit-only API has nothing to do with that, it only gives an access to a restricted lease of space. Websockets only allow your app to talk with its mothership and its friends, not other apps working locally. Sure. They won't allow me to connect two computers behind a NAT with SSH. Nope, only certain fraction of their output. There is no option to configure them, and sharing policies do not exist. I was thinking about a way to squeeze few things on one screen; most webapps are designed to work full-screen, at most giving you a chance to open a tab. BTW WebGL is a giant security hole because for years of GPU development no-one imagined that low-level access can be given to an untrusted code. Great, but 95 in 100 of such innovations are total failures, 99 in 100 break keyboard navigation and accessibility, finally 999 in 1000 have zero personalisation options. That's not the point; they give me a chance to switch to other, working app and continue using the service/data.