But Kevin, you never really answered the question of the article. Unless I
need a truly-masterless p2p topology, why would I do all this stuff, including throw away editor intent around things like block split, just to use Yjs? prosemirror-collab and prosemirror-collab-commit already seem to do all the things the Yjs docs
claim to do (unbounded offline writes that reconcile automatically, optimistic updates, tolerant of all kinds of failures), and they work with 100% fidelity to the underlying model. AFAICT, the
only thing that you
need Yjs for, is true p2p editing.
This is a serious question, and the question of the article. I am here to learn what you mean, please explain.
This is a serious question, and the question of the article. I am here to learn what you mean, please explain.