←back to thread

Learn Yjs Interactively

(learn.yjs.dev)
296 points paulgb | 5 comments | 16 Jan 25 22:13 UTC | HN request time: 0.619s | source
Show context
adeptima ◴[17 Jan 25 06:56 UTC] No.42734827[source]▶
Yjs is nice. Easy to get p2p results.

Yjs backend, its persistence, eventual conflict resolution (one of editors stayed too long offline), history rewind seems like a tough engineering challenge to crack.

Always wanted to have a nice experience with block editor like Platejs https://platejs.org/

There are nice attempts simplify dev experience with solutions like Liveblocks https://liveblocks.io/text-editor However most options come at the expense of controlling your data.

CRDT keyword search on HN bring consistently good results and interest in the topic, but no good options on open source backend side. Checked it many times in the past. Please correct me if I missed something.

https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=tru...

Most people expectations it should work at least as in Google Docs or Notion, and on the dev side it should be store privately in Postgres JSONB like format without going deep into details.

replies(1): >>42734910 #
1. blixt ◴[17 Jan 25 07:15 UTC] No.42734910[source]▶
I agree. In theory you need to just distribute serialized patches but in a real world backend scenario you may need to integrate with knowledge of current document state, user identity, and possibly even some level of access control.

I’ve wanted to use Y.js with a Go backend multiple times but gave up each time due to time constraints as it’s hard to find simple reference implementations.

I’ve been checking back over the years but it still seems hard to do this outside of Node.js.

replies(2): >>42735159 #>>42735191 #
2. adeptima ◴[17 Jan 25 08:06 UTC] No.42735159[source]▶
Same experience. Go is my default choice for backend too

It can easily be a full time job

You need to mirror all logic and encoding/decoding part

https://github.com/yjs/yjs/blob/main/src/utils/encoding.js

https://github.com/yjs/yjs/commits/main/src/utils/encoding.j...

I was thinking about spining off nodejs instance just for persistence and syncing with postgres

replies(1): >>42737355 #
3. 5Qn8mNbc2FNCiVV ◴[17 Jan 25 08:11 UTC] No.42735191[source]▶
Fyi, building a collaborative editor right now and it's still hard to do outside of Node
replies(1): >>42735238 #
4. adeptima ◴[17 Jan 25 08:22 UTC] No.42735238[source]▶
Still better time spend than doing leetcode.

It's my go-to argument against leetcode style interviews.

I would rather ask a candidate to spend 30 mins and do research together on collaborative editing, or visualizing distances used in pgvector or similar vector database.

Imagine how far the whole colabarative editing space moved forward if 1% of leetcode grinding were rerouted

5. jakelazaroff ◴[17 Jan 25 13:36 UTC] No.42737355[source]▶
Author here — I think our own almost server is almost exactly what you’re looking for? Y-Sweet [1] is open source, written in Rust and persists documents to S3. We offer a hosted version if you want to quickly check it out, which you can use with your own S3 bucket if you want to self host eventually.

This is the first I’ve heard of Platejs, but we do have a tutorial on integrating a block editor using BlockNote [2]

[1] https://github.com/jamsocket/y-sweet

[2] https://docs.jamsocket.com/y-sweet/tutorials/blocknote