one big difference:
- DataStore is journal-like sync (they have revisions and you can replay changes from a certain
- our sync system is more like a Merkle-tree (https://en.wikipedia.org/wiki/Merkle_tree). We don’t have a real proper Merkle-tree because we don’t enforce that our ETags be cryptographic hashes of the content, and because all ETags are assigned on the central server-node instead of on the node where the content is created, but the idea is definitely similar.
in the DataStore API, each store seems to be just like an array of objects, you can loop over it from object 0 to object
store.getLength()-1. we have the path strings as identifiers, which allows richer storing of data into collections (folders), and gives the option to sync only part of the tree.
so i propose not to switch to the DataStore API. i think the space is unexplored and big enough for remoteStorage as well as PouchDB as well as DataStore. next year we can compare notes again and see where all three stand in terms of adoption.