DString implementation needs rework

[marcus-pousette]

The current implementation of DString is like a canvas. Anyone can write anywhere on the canvas by inserting string at an offset with length. The current implementation does not support efficient deletion by pruning the DAG, the operation data type itself does not out of the box support this.

Consider instead the xi-editor that uses the rope data structure

Regarding xi-editor, here is some interesting discussion/critique on the implementation that xi-editor brings forward.

[Erudition]

Consider also the approach taken by Diamond Types:
https://github.com/josephg/diamond-types

As seen in https://josephg.com/blog/crdts-go-brrr/

and the deletion strategy used by Replicated Object Notation:
http://replicated.cc/rdts/rga/

[marcus-pousette]

Yea! I have going back and forth through all these for some time.. In order to get it to work with Diamond types one need to find a nice integration with the log implementation that already exist in this repo (which has many very nice memory optimizations for recovering from disc, especially in the browser).

[marcus-pousette]

and the deletion strategy used by Replicated Object Notation:
http://replicated.cc/rdts/rga/

Have not seen this, interesting!