Re: "Browsers need to be completely overhauled to properly deal with network errors and retries". This is not a browser-land problem, it's a developer-land pro

Re: "Browsers need to be completely overhauled to properly deal with network errors and retries". This is not a browser-land problem, it's a developer-land problem. Developers simply need to start writing HTML5 apps as distributed applications. And this is where browsers need to assist developers: 1. websocket performance in Chrome is poor (http://code.google.com/p/chromium/issues/detail?id=123228 http://code.google.com/p/chromium/issues/detail?id=123228) 2. IndexedDB is at least an order of magnitude slower than LevelDB, and read transactions block read transactions (!) (http://code.google.com/p/chromium/issues/detail?id=128865 http://code.google.com/p/chromium/issues/detail?id=128865) 3. There's no way for a user to grant unlimited storage permissions without going through a proprietary web store and registering as a user of a third party company. 4. There's no support for first-class binary keys in IndexedDB. 5. LocalStorage is broken. 6. Data api in WebRTC is of lesser priority than video/audio (should be the other way round, in fact providing UDP or TCP directly with appropriate permissions would solve this more elegantly). Browsers must provide primitive CS APIs. TCP, UDP, and POSIX, all as per the Node.js api, with the user granting permissions. There has been a tendency for the web specs to optimize towards protecting developers and users from "shooting themselves in the foot". The web specs need to be written from the point of view of enabling the next operating system. They need to give more power to developers and to users. Browsers are hoarding the problem and ruining the solution in the process, by trying to solve something that can only be solved higher up in the stack. Instead they should enable things to be done in the most direct way possible with a minimum of red tape. The web specs have tended to go for simplicity instead of directness. But directness is better than simplicity. The trend of writing HTML-5 to do list demos needs to give way to writing HTML-5 operating system demos.