czx111331

9 ms·

1.
Lody: A Local-First Workspace for Teams and Coding Agents(lody.ai)
2 points by czx111331 1mo ago|0 comments
2.
CRDTs merge concurrent edits. Why not concurrent creation?(loro.dev)
31 points by czx111331 4mo ago|3 comments
3.
by czx111331 11mo ago
Perhaps the most important difference is that software — even after being purchased and used — remains relatively easy to patch, unlike a physical lock.
4.
by czx111331 1y ago
loro-prosemirror[1] offers much better support for integrating Loro with ProseMirror/Tiptap. In theory, loro-mirror could also be used to integrate Loro with other rich-text editors, but that wasn’t its original design goal and it may
5.
by czx111331 1y ago
I believe that in the right contexts—specifically where eventual consistency is acceptable—the local-first paradigm is highly valuable and will gradually become mainstream. A major factor limiting adoption today is that existing local-first
6.
Loro Mirror: Make UI State Collaborative & Local-First by Mirroring to CRDTs(loro.dev)
3 points by czx111331 1y ago|0 comments
7.
Qrs: Stream data through multiple series of QR codes(github.com)
1 points by czx111331 2y ago|0 comments
8.
Loro 1.0: A High-Performance CRDTs Library with Version Control(loro.dev)
10 points by czx111331 2y ago|0 comments
9.
MoonBit native, up to 15x faster than Java in numerics(moonbitlang.com)
2 points by czx111331 2y ago|0 comments
10.
Collaborative text editing with Eg-Walker: Better, faster, smaller(arxiv.org)
251 points by czx111331 2y ago|31 comments
11.
Collaborative text editing with Eg-Walker [video](youtube.com)
2 points by czx111331 2y ago|0 comments
12.
by czx111331 2y ago
Is Bitcoin a "public sync" application by the definition?
13.
by czx111331 2y ago
The implementation can indeed combine multiple different CRDTs. Within Loro's internal implementation, each op does need to store a parent ID. However, as Seph mentioned, consecutive operations under the same parent can be effectively
14.
Movable tree CRDTs and Loro's implementation(loro.dev)
286 points by czx111331 2y ago|29 comments
15.
CRDT: Movable Trees(loro.dev)
10 points by czx111331 2y ago|2 comments
16.
by czx111331 3y ago
We are carefully stabilizing our encoding format and will have a clear storage format documentation introduced in version 1.0. I agree that a more transparent format can provide users with a better sense of control, and we will try to creat
17.
by czx111331 3y ago
Similar to OT, in certain scenarios, it's sufficient to ensure that only a subset of peers have the complete data, while others don't need the full history. For instance, in real-time collaboration scenarios with a central server,
18.
by czx111331 3y ago
> If you remove these ops from history, does that remove the ability to time travel (per the home page "An antidote to regret, enabling historical edits traversal") or merge branches? Yes. But squash can be supported. > How
19.
Loro's rich text CRDT(loro.dev)
207 points by czx111331 3y ago|47 comments
20.
by czx111331 3y ago
Yes, it's agnostic to the network layers. The output of doc.exportFrom() is just a binary array.
21.
by czx111331 3y ago
We are addressing the CRDT downsides mentioned in the article at Loro: - Ever-growing state. This is no longer an issue. With OT-like CRDTs, you can discard unnecessary historical data at any time. This is theoretically feasible, and we are
22.
by czx111331 3y ago
The code in the blog is from Vue Pinia, a state management library, and not from Loro. It serves as an example demonstrating that CRDTs can be modeled similarly. Thus, you might expect to use Loro in a similar way. Indeed, schema migration
23.
Loro: Reimagine state management with CRDTs(loro.dev)
247 points by czx111331 3y ago|43 comments
24.
by czx111331 3y ago
Nice work! However, it doesn't seem like a fair benchmark. It doesn't calculate and store the ops, nor does it store the actual text. To build a text CRDT with delta updates support upon it, users must store OpID => Text in an
25.
by czx111331 3y ago
Yeah, I'm referring to this. In essence, it's like a mind map that expands from left to right in a compact format. There are similar things like Logseq and Roam Research. Although the view is designed mostly for text, I think it i
26.
by czx111331 3y ago
Thanks for sharing. I might be able to build upon this.
27.
by czx111331 3y ago
Probably little. Because the tree is flat and wide, different tree layout algorithms have little effect on the overall compactness. However, I guess it might be improved by using an outline view like Workflowy.
28.
by czx111331 3y ago
Yes, I use a similar approach when debugging some parts of my CRDTs as well. It's very helpful. However, this algorithm is designed specifically for trees. I'm not sure whether I could manage to make it work on DAGs (Directed Acyc
29.
by czx111331 3y ago
Probably not. This algorithm is specifically designed for trees, not graphs.
30.
by czx111331 3y ago
PRs are welcome! I wasn't aware that Diamond types also provided a WASM version. I've included it in the native benchmark with Loro though. You can see it here: https://www.loro.dev/docs/performance/nativ

More ›