automerge VS rustpad

Thank you! I actually kind of cheated and didn't have to implement any of that myself because Firebase took care of it. But when I was considering how to build Calenday, those were on my mind. I had read about CRDTs on Figma's blog (https://www.figma.com/blog/how-figmas-multiplayer-technology...) and was considering using something like this to ease the burden on implementation: https://github.com/automerge/automerge

Looks pretty similar to https://rustpad.io/

Awesome! I requested this in rustpad but it was closed with wontfix. I suppose it is out of scope of rustpad but I'm really glad to see that there's this project to add it.

I used rustpad's backend, and documents are transient, meaning that they will be lost between server restarts or after 24 hours of inactivity.

Just adding an example to the other side, I wrote https://rustpad.io/ in Rust, which is a collaborative text editor that uses WebSockets and resolves edit conflicts in real time using an operational transformation algorithm. It's a fairly complex bit of logic. But I actually thought Rust was the best language for this application because of performance, data race-safety, Serde, and the borrow checker. (My second choice would have been Go with stress tests run under `the -race flag.)

Also check out Rustpad (Github) - it has collaborative editing implemented now.

Rust has great support for web backend, but not as easy as something like Node.js due to a less mature ecosystem of libraries. I've done React+Rust as a stack before (see Rustpad), but this was a very particular use case (stateful network WebSocket service). For most full-stack applications I'd use something like Next.js instead.

https://rustpad.io/ sorry my bad