yjs VS MobX

No back-end. Data is shared via WebRTC directly between connected browsers. I'm using Yjs to help me with that.

also there is this Javascript library that implements Conflict Resistant Data Types

There are a lot of implementations of CRDTs out there. In JavaScript, for instance, we have Y.js (https://github.com/yjs/yjs) and automerge (https://github.com/automerge/automerge). There’s also a Y.js demo (https://demos.yjs.dev/prosemirror/prosemirror.html) that allows you to play around with them and have your own collaborative app running in just a few seconds. All messages are exchange via webRTC and manages the state via CRDTs. This can be a great sandbox to understand how CRDTs work and see.

Yjs is being quite heavily used in the industry[1], and being researched for even more companies. There are also demos showing how to integrate it with an existing rich text editors[2]. If you have some ideas about the missing parts, you could also open topic on discuss.yjs.dev - the documentation page (https://docs.yjs.dev) has tons of useful links.

Re. other purpose projects - Yjs/Yrs main target are sequential data structures (text, arrays), but it also has support for maps and xml-like elements. In general you can build most data structures with it. I agree that it would be nice to have some other applications in demos though.

[1] https://docs.yjs.dev/yjs-in-the-wild

Anyone unsure of what a CRDT is, this is the perfect intro: https://www.inkandswitch.com/peritext/

The two most widely used CRDT implementations (combining JSON like general purpose types and rich text editing types) are:

- Automerge https://github.com/automerge/automerge

- Yjs https://github.com/yjs/yjs

I've always been curious about real-time multiplayer user interfaces.

When I found out about CRDTs and Yjs[1] I thought they could serve as a solid base for a project like that.

So I built this pretty simple desktop-like UI (heavily inspired by lifeat.io) and used Yjs to replicate the whole UI state among multiple peers, creating the experience of a unique interface.

Try online: https://yboard.lol

[1]: https://github.com/yjs/yjs

[4]: https://github.com/yjs/yjs

But I want to impress upon you that this is just only one of many patterns you can use this hook for. While this is subjective, I am personally not a huge fan of Redux and this type of pattern. It has its merits, but I think once you want to start layering in new patterns for actions, Mobx, Zustand, or XState are preferable in my personal opinion.

It's important to note that Redux is just one of many options for global state management in a React application. Other popular options include MobX and the React context API.context API](https://reactjs.org/docs/context.html).

MobX - or even MobX-state-tree if you prefer

MobX

It's silly to deny that in comparison with Redux, MobX's community is not so big. For example, the number of downloads at npmjs.com for Redux is 8 times bigger than for MobX. However, I can hardly agree with the other disadvantages.

I used https://mobx.js.org s lot. Concepts are a bit different because it is based on observables and your state is mutable, but really small boilerplate, fast and fun to work with

Kada imamo potrebe za optimizacijom rirenerovanja komponenti u React-u i radimo sa velikim i kompleksnim objektima (deeply nested objects) biblioteke kao Redux nisu najoptimalnije i verovatno je najbolje koristiti proxy state management: MobX ili Valtio.

I guess it's similar to this MobX :)? https://github.com/mobxjs/mobx

MobX is exactly what you're looking for: https://github.com/mobxjs/mobx

Vue works similar to React + MobX, but with weird design decisions like implicit reactivity, and a stale ecosystem thanks to the Vue2 vs Vue3 debacle.