crdt-woot
dotted-logootsplit
Our great sponsors
| crdt-woot | dotted-logootsplit | |
|---|---|---|
| 2 | 2 | |
| 14 | 43 | |
| - | - | |
| 0.0 | 0.0 | |
| about 1 year ago | 4 months ago | |
| TypeScript | TypeScript | |
| - | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
crdt-woot
We haven't tracked posts mentioning crdt-woot yet.
Tracking mentions began in Dec 2020.
dotted-logootsplit
- Evan Wallace CRDT Algorithms
-
5000x Faster CRDTs: An Adventure in Optimization
Yes, xray was abandoned and teletype is written in JS.
I understand your point and as a researcher and engineer I know your feeling. I took some cautions by using "Some optimizations". I value engineering as much as research and I'm bothered when I heard any side telling the other side that their work is worthless. Your work and the work of Kevin Jahns are very valuable and could improve the way that researchers and engineers do benchmarks.
This is still hard for me to determine when position-based list CRDT (Logoot, LogootSPlit, ...) are better than tombstone-based list CRDT (RGA, RgaSplit, Yata, ...). It could be worth to assess that.
3 year ago I started an update of LogootSplit. The new CRDT is named Dotted LogootSplit [1] and enables delta-synchronizations. The work is not finished: I had other priorities such as writing my thesis... I have to perform some benchmark. However I'm more interested in the hypothetical advantages of Dotted LogootSplit regarding synchronization over unreliable networks. From an engineering point-of-view, I'm using a partially-persistent-capable AVL tree [2]. Eventually I would like to switch to a partially-persistent-capable b-tree. Unfortunately writing a paper is very time consuming, and time is missing.
I still stick with JS/TS because in my viewpoint Wasm is not mature yet. Ideally, I would like to use a language that compiles both to JS and Wasm. Several years ago I welcomed Rust with a lot of enthusiasm. Now I'm doubtful about Rust due to the inherent complexity of the language.
[1] https://github.com/coast-team/dotted-logootsplit/tree/dev
What are some alternatives?
yjs - Shared data types for building collaborative software
teletype-crdt - String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.
diamond-types - The world's fastest CRDT. WIP.
osmosis-js - JS reference implementation of Osmosis, a JSON data store with peer-to-peer background sync
crdt-benchmarks - A collection of CRDT benchmarks
SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
automerge - A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
FluidFramework - Library for building distributed, real-time collaborative web applications
cow-list - Copy-On-Write iterable list
citrea-model - A CRDT-based collaborative editor engine of letters.yandex.ru (2012, historical)
peritext - A CRDT for asynchronous rich-text collaboration, where authors can work independently and then merge their changes.