guillaumesalles

6 ms·

1.
by guillaumesalles 4y ago
By "other use cases", are you talking about apps that are not design tools like Notion or Google Spreadsheet? Or other edge cases related to undo/redo?
2.
by guillaumesalles 4y ago
To summarize the differences between Ably/Pusher and Liveblocks, Ably/Pusher use a centralized Redis to broadcast messages to channels. Liveblocks has tiny isolated servers on the edge for every room. These two different architect
3.
by guillaumesalles 4y ago
Our code client does not depend on any front-end technology, so you can use it with Svelte or Vue. We have a few examples that use Vue and Svelte here: https://github.com/liveblocks/liveblocks/tree/main/e
4.
by guillaumesalles 4y ago
For rich text editing, undo should probably reset the scroll position and the cursor close the edit you're undoing. I think reseting the time position would also make sense for video editing. So basically, it's a way to get back a
5.
by guillaumesalles 4y ago
Yes that's good way to implement it! But I'm still not sure this is the default behavior that we want, even it's only for deletion. I think it's more of a UX problem than an engineering problem as explained here: https:
6.
by guillaumesalles 4y ago
Yes! We're using Durable Object under the hood :) Thanks to you for providing such a great platform!
7.
by guillaumesalles 4y ago
It's technically possible by caching only deleted shapes if any operations in the undo stack are associated with them. But is it really the UX we want every time it's happening? Let's imagine that we work together on a design
8.
by guillaumesalles 4y ago
I worked on the implementation so don't hesitate if you have deeper technical questions that the article is not covering :)
9.
by guillaumesalles 5y ago
Hey CTO and co-founder at Liveblocks here :wave: Happy to answer any technical questions!
10.
by guillaumesalles 5y ago
Like Yjs, our Storage block is CRDTs based, but we're making different trade-offs. For example, our CRDTs are not "pure" so we solve some conflicts on the server. Also, we don't support Text CRDTs yet. But Liveblocks is
11.
by guillaumesalles 5y ago
I just answered the Durable Objects question here https://news.ycombinator.com/item?id=27998674 I didn't evaluated fly.io but from their website, it definitely looks promising! I will try it for sure!
12.
by guillaumesalles 5y ago
Thanks for the kind words :) Nice catch! All the examples that you see on our website are using Cloudflare Durable Objects! But because they are limited, we also have a version of our server that works on AWS some of our customers.
13.
by guillaumesalles 5y ago
Good question! There are still a lot of specialized editors that are not text-based nor collaborative yet. In the creative space, we can imagine 3D collaborative editors (think Figma but for 3D). Here is an example built with liveblocks: h
14.
by guillaumesalles 5y ago
Thanks for the kind words :) From what I understand from Replicache, it focuses only on conflicts resolution with CRDTs, and it does not come with a web socket infrastructure nor a hosted backend. You need to have your own servers or use ex
15.
by guillaumesalles 5y ago
From our experience, live cursors positioning depends on the use case and the content behind them. For a "canvas app" (like Figma), the positioning will be absolute with an offset depending on the panning. For a responsive website
16.
by guillaumesalles 5y ago
Hi! Great questions :) Liveblocks does not come with a specific UI. We're providing APIs to create rooms and share states between users. The state can be volatile (like cursors, focused input, selection) or persisted even when the sess
17.
by guillaumesalles 5y ago
Hi Gys, co founder of Liveblocks here! Our goal is to help companies create collaborative products like Figma or Google Docs with API and guides. Multiplayer infrastructure and conflicts resolutions can be challenging to build in-house and