yonote/yjs
24
0
Fork 0
Code Pull Requests 1 Releases Activity

Add missing word

Browse Source
This commit is contained in:
Joakim 2022-11-05 21:15:33 +01:00 committed by GitHub
parent a64c51ec06
commit d7751c16fd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -1060,16 +1060,17 @@ More information about the specific implementation is available in
[INTERNALS.md](./INTERNALS.md) and in [INTERNALS.md](./INTERNALS.md) and in
[this walkthrough of the Yjs codebase](https://youtu.be/0l5XgnQ6rB4). [this walkthrough of the Yjs codebase](https://youtu.be/0l5XgnQ6rB4).
CRDTs that suitable for shared text editing suffer from the fact that they only grow CRDTs that are suitable for shared text editing suffer from the fact that they
in size. There are CRDTs that do not grow in size, but they do not have the only grow in size. There are CRDTs that do not grow in size, but they do not
characteristics that are benificial for shared text editing (like intention have the characteristics that are benificial for shared text editing (like
preservation). Yjs implements many improvements to the original algorithm that intention preservation). Yjs implements many improvements to the original
diminish the trade-off that the document only grows in size. We can't garbage algorithm that diminish the trade-off that the document only grows in size. We
collect deleted structs (tombstones) while ensuring a unique order of the can't garbage collect deleted structs (tombstones) while ensuring a unique
structs. But we can 1. merge preceeding structs into a single struct to reduce order of the structs. But we can 1. merge preceeding structs into a single
the amount of meta information, 2. we can delete content from the struct if it struct to reduce the amount of meta information, 2. we can delete content from
is deleted, and 3. we can garbage collect tombstones if we don't care about the the struct if it is deleted, and 3. we can garbage collect tombstones if we
order of the structs anymore (e.g. if the parent was deleted). don't care about the order of the structs anymore (e.g. if the parent was
deleted).
**Examples:** **Examples:**