News for hackers. Stuff that matters.
Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by josephg on Monday May 22, 2023 @06:54PM (#36037729)
Author of Diamond types (and the data sets you’re using) here! Congratulations on getting this insane performance. I’d love to know how you’re doing it - that’s truly excellent work. I didn’t know it was even possible to get javascript to go that fast on this problem. And I say that as someone who has thought about crdt / text performance way more than is reasonable.

RIP my morning. I’m going to have to pour through your code to see how you’ve pulled this off. Do you have anything you recommend I read to understand how your algorithm works?

Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by streamich on Monday May 22, 2023 @07:16PM (#36037918)
> Do you have anything you recommend I read to understand how your algorithm works?

Not really, you should already know those. It is just Block-wise RGA with a tree for blocks and a tree for identifiers, also, with split link and insert-in-between optimization from Briot et. al (2016).

Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by streamich on Monday May 22, 2023 @07:20PM (#36037950)
A sneak peak to some future blogpost, this is what happens when "OOD " is inserted into "GG WP" to get "GOOD G WP":

https://appsets.jsonjoy.com/blogposts/list-crdt-internals/wi...

Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by bxff on Tuesday May 23, 2023 @11:19AM (#36045564)
Can't wait for the future blogpost! I got the Rope text data structure both from the pic, and from the data structure in AbstractRga, but am unsure of the identifier table, I am guessing thats the ID -> Chunks binary tree.
Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by streamich on Tuesday May 23, 2023 @12:28PM (#36046634)
Subscribe to our mailing list to not miss it: https://jsonjoy.substack.com/
Re:JSON-joy CRDT benchmarks, 100x speed improvement over sta... by bxff on Sunday June 04, 2023 @09:29PM (#36191245)
Any ETA on the blog post?