5 ms·

There are a few of those frameworks. The first one that comes to mind is YJS here is a getting started[1]. 1. https://www.tag1consulting.com/blog/deep-dive-real

There are a few of those frameworks. The first one that comes to mind is YJS here is a getting started[1]. 1. https://www.tag1consulting.com/blog/deep-dive-real-time-collaborative-editing-solutions-tagteamtalk-001-0 https://www.tag1consulting.com/blog/deep-dive-real-time-coll...

sambroner 5y ago
YJS (and Kevin Jahns!) is fantastic, although I'm not sure they're interested in addressing all of these problems. In so far YJS has been very focused on replicating state from one place to another. And the parent comment may be making light of some of the big issues in the space. You need to be generic, but also performant and simple compared to the competition. Real time text editing is not trivial although there's solid prior art now. Even undo management is a whole problem space (what should a cross user undo look like if there have been dependent changes).
- kevinjahns 5y ago
  Yjs is exactly that. It is a simple abstraction for building any kind of collaborative application. It has ready to use solutions for most problems related to this problem space. The selective UndoManager, for example, is generic&configurable and can be reused for all kinds of stuff. It supports many different editors. It supports many different (scalable) backends. It is much more than state synchronization. If there is anything missing, then let's work on it. Yjs is extensible and allows for custom features that others can reuse.
kybernetikos 5y ago
Do you know if any of these frameworks support different users being permissioned to see different documents or different views of collections.
- sambroner 5y ago
  Fluid Framework (a project I contribute to/work on through Microsoft) supports this via token in our default service implementation, but we don't have integration with an ACL DB.

5 ms·

There are a few of those frameworks. The first one that comes to mind is YJS here is a getting started[1]. 1. https://www.tag1consulting.com/blog/deep-dive-real

by pumanoir 5y ago

sambroner 5y ago
YJS (and Kevin Jahns!) is fantastic, although I'm not sure they're interested in addressing all of these problems. In so far YJS has been very focused on replicating state from one place to another. And the parent comment may be making light of some of the big issues in the space. You need to be generic, but also performant and simple compared to the competition. Real time text editing is not trivial although there's solid prior art now. Even undo management is a whole problem space (what should a cross user undo look like if there have been dependent changes).
- kevinjahns 5y ago
  Yjs is exactly that. It is a simple abstraction for building any kind of collaborative application. It has ready to use solutions for most problems related to this problem space. The selective UndoManager, for example, is generic&configurable and can be reused for all kinds of stuff. It supports many different editors. It supports many different (scalable) backends. It is much more than state synchronization. If there is anything missing, then let's work on it. Yjs is extensible and allows for custom features that others can reuse.
kybernetikos 5y ago
Do you know if any of these frameworks support different users being permissioned to see different documents or different views of collections.
- sambroner 5y ago
  Fluid Framework (a project I contribute to/work on through Microsoft) supports this via token in our default service implementation, but we don't have integration with an ACL DB.