liveblocks VS Socket.io

Absolutely! The real complexity comes from conflict resolution. If someone edits the top, and someone else edits the bottom, which version do you go with? What if they're editing the same area? Entire companies exist to provide elegant solutions to this[0], so it's no simple task.

0: https://liveblocks.io/

I can imagine, browser extensions are a pain in the butt. Are you planning to open source the code? Did you build everything by yourself or on top of https://liveblocks.io/?

For the following example, I want the gradient color to flow from "Hello World" to the "Circle", so they are synchros and match the colors. I created this snippet but I'm having trouble with the rest. https://play.tailwindcss.com/accHTivCcx. Another example would be the https://liveblocks.io/'s title, which flows through the colors in the gradient. How would I achieve this?

Does anyone have any opinions about using Liveblocks for a live collaboration application as opposed to just using Firebase?

liveblocks is great for multiplayer state sync. i was able to make my canvas redux app collaborative in a couple of hours https://liveblocks.io

Very cool use case for CRDTs! I've seen a bunch of different use cases from other products like https://liveblocks.io/ and https://electric-sql.com/. It's interesting how CRDTs are now taking hold so much for all these collaborative syncing scenarios. Wonder what's driving the proliferation now given they've been around for awhile?

Hi Tim,

I'm a bit biased but https://liveblocks.io is great for that :)

If you know how to use React, that's pretty much all you need to know. It also includes some nice hooks to enable things like multiplayer undo/redo and live cursors.

The team even put a couple of interactive blog posts about that that you might find interesting:

True! I would also include https://liveblocks.io to that list of services that help developers make multiplayer experiences.

Interesting to see more players in this space to help more and more developers do this.

The first is the script tag in the head of our HTML document that loads the Socket.IO client library. This script tag includes the Socket.IO client library that will communicate with our socket.io server from the code above.

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

Nextjs + socket.io.. Planning to use webrtc for video calls later

Implementação em Node usando Socket.io

I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture.

yes. Im running on DreamCompute currently. Discord.js and socket.io within same app. A dedicated server works too, but pricier.

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).