7 ms·

The File System Access API seems promising.

• jsheard 3y ago
  I'm not sure more APIs are the solution, LocalStorage could already theoretically fill the role of a persistent large data store if browsers didn't cap the storage at 5-10MB for UX reasons. Removing that cap would require user facing changes to allow them to manage the storage used by sites and clean it up it manually when it inevitably gets bloated. Any new API which lets sites save stuff on the client is going to have the same issue.
  • fauigerzigerk 3y ago
    >Any new API which lets sites save stuff on the client is going to have the same issue. I don't think it would have the same issues, because the files could be stored in a user specified location outside the browser's own storage area. Browser vendors can't just delete stuff that may be used by other software on a user's system. And they cannot put a cap on it either, because users can store whatever they like in those directories, bypassing the browser entirely. But I have never used this API, so maybe I misunderstand how it's supposed to work.
    • jsheard 3y ago
      If that's how it works then it would avoid the problem I mentioned, but the UX around using that to cache data internal to the site implementation sounds pretty terrible. You click on "Listen to this article" on a webpage and it opens a file chooser expecting you to open t2s-hq-fast-en+pl.model if you already have it? Users won't be able to make any sense of that.
      • fauigerzigerk 3y ago
        The API (or at least the Chrome implementation) appears to be unfinished, but the plan seems to be to eventually support persistent directory permissions. So the web app could ask the user to pick a directory for model storage and henceforth store and load models from there without further interaction.