> Getting rid of native SQLite in Chrome (Firefox was forced to follow), with the main reason is that ,,there are no 2 different implementations, all browsers u

> Getting rid of native SQLite in Chrome (Firefox was forced to follow), with the main reason is that ,,there are no 2 different implementations, all browsers use the same''. You have that backwards, it was Mozilla arguing against WebSQL (and never implementing it in Firefox in the first place) and Google was arguing for it. I agree with your point about file system persistence, that is probably the biggest limitation in web apps compared to native apps today. However again it was Google arguing in favor of the File System Access API (letting web apps read/write normal files) and Mozilla/Apple arguing against it and only supporting a neutered version (fake hidden files that the browser can delete whenever it wants).