Add KV Storage Built In Module

[kitsonk]

In Chromium 74, KV Storage has been implemented as a built-in module. The module is a far more rational API than IndexDB (and local storage).

The WICG draft is located here: https://wicg.github.io/kv-storage/

This would require #1922

This could negate the need for #1699

[kitsonk]

Actually reading the spec further, it is actually a standard modern API layer on top of IndexDB and uses IndexDB to persist the storage. So #1699 is a requirement before we could implement this.

[afinch7]

Doesn't mean that we have to implement it like that.

[kitsonk]

Well, if you look at the spec, there is a expected back off to IndexedDB where you can gain access to the db instance for advanced usage.

[afinch7]

They way you put it the first time it sounded like it was just a implementation choice, but no it actually exists in the spec https://wicg.github.io/kv-storage/#storagearea-backingstore.
That seems like a really questionable design choice if you ask me. We might have been at a point where IndexDB could be deprecated in favor of a promise based standard, but now one of the most questionable web APIs has another silly reason that it has to exist other than "for legacy applications". The point of an API is not to dictate implementation. This API is almost directly dependent on it's implementation. What happens when the way that x browser stores this information in IndexDB is not exactly the same as y browser? Is the idea to have a js module that works on all browsers? If that was the case why not just release it as a standalone js library? I like the idea of a more modern alternative to localStorage, but this seems like a really bad way to go about it.

[kitsonk]

What happens when the way that x browser stores this information in IndexDB is not exactly the same as y browser?

Well that is part of the IndexDB spec.

[afinch7]

I meant the KV Storage implementations not the browser itself.

[kitsonk]

I meant the KV Storage implementations not the browser itself.

That is also in the draft spec... Like the ordering of keys, etc. There are a couple concerns regarding this layering though which are also addressed in the draft spec: https://wicg.github.io/kv-storage/#perfect-polyfill

[kitsonk]

No browsers now intend to implement this, so work is suspended: https://github.com/WICG/kv-storage#status

We shouldn't consider implementing until there is further movement.