- dotted-logootsplit VS crdt-woot
- dotted-logootsplit VS diamond-types
- dotted-logootsplit VS crdt-benchmarks
- dotted-logootsplit VS transcribee
- dotted-logootsplit VS SyncedStore
- dotted-logootsplit VS peritext
- dotted-logootsplit VS cow-list
- dotted-logootsplit VS awesome-crdt
- dotted-logootsplit VS automerge
- dotted-logootsplit VS teletype-crdt
Dotted-logootsplit Alternatives
Similar projects and alternatives to dotted-logootsplit
-
-
Civic Auth
Auth in Less Than 5 Minutes. Civic Auth comes with multiple SSO options, optional embedded wallets, and user management — all implemented with just a few lines of code. Start building today.
-
automerge
A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
-
peritext
A CRDT for asynchronous rich-text collaboration, where authors can work independently and then merge their changes.
-
-
-
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
SyncedStore
SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
-
-
-
teletype-crdt
Discontinued String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.
-
dotted-logootsplit discussion
dotted-logootsplit reviews and mentions
- 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
Stats
coast-team/dotted-logootsplit is an open source project licensed under Mozilla Public License 2.0 which is an OSI approved license.
The primary programming language of dotted-logootsplit is TypeScript.