in one sense it's cool. So congrats on that.
I wonder though - if it's not as good at updating the DOM as other libraries - what is it's real "place" in the ecosystem?
Is it doing more than wrapping over IndexedDB / LocalStorage?
I'd say, a nice wrapper for IndexedDB is a welcome thing (looks like minimongo already does that). And there's a lot of space to grow in that (providing change events, etc).
Maybe I just don't get the value prop?
Maybe the value prop only really shows up when you integrate the data binding? So it's sort of like reactive programming but based on a structured data store, instead of raw JS objects?
Is it doing more than wrapping over IndexedDB / LocalStorage?
I'd say, a nice wrapper for IndexedDB is a welcome thing (looks like minimongo already does that). And there's a lot of space to grow in that (providing change events, etc).
Maybe I just don't get the value prop?
Maybe the value prop only really shows up when you integrate the data binding? So it's sort of like reactive programming but based on a structured data store, instead of raw JS objects?