1. 7

  2. 3

    not clear the problem this thing solves

    1. 3

      So for me, I’m very excited since browser-local storage has historically been a real PITA for developers. If I can do something really nice like this in Chrome, which most users at my company rely on, it’ll improve my life significantly.

      EDIT: Also this exists: localForage

      1. 2

        This helped me out: https://github.com/WICG/kv-storage.

      2. 2

        The API is nice! Looks super slick to use, congrats to you and to the team.

        The WICG RFC provided a lot of the details I was looking for here as well, it’s a nice secondary info source: https://github.com/WICG/kv-storage. Cool that this is being done jointly with W3C and the original IndexedDB contributors.

        1. 1

          i feel like they kind of glossed over what is so bad about IndexedDB

          im not arguing the point as i dont know enough about it - but is it really worth making a new API because the old one is arbitrarily “bad”? why cant they just improve IndexedDB?


          1. 2

            IndexedDB API is powerful, but may seem too complicated for simple cases. If you’d prefer a simple API, try libraries such as localForage, dexie.js, ZangoDB, PouchDB, and JsStore that make IndexedDB more programmer-friendly.

            They’re essentially making another simple localstorage-like-but-async wrapper, but shipped with the browser already

          2. 1

            You can actually use built-in modules in your code today, with the help of another new feature called import maps

            Are they actually implemented somewhere already? Chromium behind a flag?