[caryfitz]

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?

[coolbloke1324]

> if it's not as good at updating the DOM as other libraries

ForerunnerDB is actually very efficient at updating the DOM, only making changes to the parts of the DOM that link to altered sections of an object / document.

> Is it doing more than wrapping over IndexedDB / LocalStorage?

Yes much more... it includes views, triggers / change events, transforms, collection joins and the obvious big one - data binding.

> 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?

This is correct and because we've been using it in production for some time we would definitely say it makes web app development a lot simpler!