Maybe you are right, but sone things I really dislike are:
- 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''.
- While there is file system implementation, there's no mmap, so there is no fast app start (just have SQLite with mmap, nothing fancy).
- No file system persistency guarantee, the OS can just wipe out the data
- All the persistent page APIs are just super hard to use compared to simple HTML/javascript/css as they are in a different process and need communication...it's overcomplicated instead of embracing a simple page as an app as an option as well.
You are right that WASM is a great improvement, and file system API is slowly coming back (still I'm not sure about mmap API which is crucial for fast app startup), but I'm talking about what was possible 10 years ago then reversed.
> 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).
- 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''.
- While there is file system implementation, there's no mmap, so there is no fast app start (just have SQLite with mmap, nothing fancy).
- No file system persistency guarantee, the OS can just wipe out the data
- All the persistent page APIs are just super hard to use compared to simple HTML/javascript/css as they are in a different process and need communication...it's overcomplicated instead of embracing a simple page as an app as an option as well.
You are right that WASM is a great improvement, and file system API is slowly coming back (still I'm not sure about mmap API which is crucial for fast app startup), but I'm talking about what was possible 10 years ago then reversed.