You don't need a CRDT to build a collaborative experience

Re:You don't need a CRDT to build a collaborative experience by jes5199 on Thursday November 16, 2023 @02:03PM (#38293832)

CRDT is a different paradigm. Ideally we'd use it to replace client-server

[ Parent | on HN ]

Re:You don't need a CRDT to build a collaborative experience by iamwil on Thursday November 16, 2023 @02:25PM (#38294133)

I think we can. Following all the implications down the rabbit hole, you end up with a system architecture where there's no front-end, and there's no back-end.

Since CRDTs are still kinda new for most people, the discussion hasn't really gotten there yet.

[ Parent | on HN ]

Re:You don't need a CRDT to build a collaborative experience by stefcoetzee on Friday November 17, 2023 @09:59AM (#38304440)

What is a good starting point to follow all the implications down the rabbit hole?

[ Parent | on HN ]

Re:You don't need a CRDT to build a collaborative experience by yencabulator on Thursday November 16, 2023 @04:21PM (#38295703)

And wrangling CRDTs into a client-server architecture is actually extra work. The basic design assumes you can trust every peer -- making sure that jes5199 actually was the peer who added a comment that is marked as author: "jes5199" is not trivial.

[ Parent | on HN ]