Did you consider JSC or v8?

No nuclear, no big hydro. Must be difficult.

That is like three or four change tracking models in the stack: diffs, xdiffs, CRDT, and likely undo/redo in the editor, unless it is unified with CRDTs

That is like three or four change tracking models in the stack: diffs, xdiffs, CRDT, and likely undo/redo in the editor, unless it is unified with CRDTs

For some reason, I expected some “resilience” perspective. Local first works when network breaks.
Maybe because of the airport outage news?

...also reproducibility, compatibility, and many other things become a lost cause.
Not the way forward.

I kept these issues in mind when designing RDX.
It is a JSON superset, CRDT-centric, diffable and patchable.
Text and binary codings with round-trip guarantee, bit-precise spec (intended). Still raw, but works.

replicated.wiki
github.com/gritzko/go-rdx

That phase was never over for me

There must be a typo. Moby Dick is 1.2M raw text.