We don't have collaboration yet, but it's the main thing we work on, and 3.0 is quietly a massive course-correction towards collaboration.
Basically, a Causality document is complex, and once multiple users edit it at the same time, if it's not done correctly, it's possible to produce gibberish data. 3.0 internally changes many things to be inherently sync-friendly.
What we want, and already have running as prototypes, is extremely real-time sync, basically <100ms sync that feels more like screen sharing, and you can be as offline or as online as you want. There's no locking and no babysitting. But this requires us to align all the data to behave in ways where you can much more just smash multiple branches of a document together and it all works out.
There would have been faster paths to sync, but they would involve compromises we found unacceptable, like locking that users have to babysit, or needing to "check in" commits. In the model you're actually getting, it's as real-time as Google Docs, but on a much more complicated document involving everybody in the same space and on the same timeline. We want to do it right so that it can handle the load of becoming a much bigger app.
Hi,
We don't have collaboration yet, but it's the main thing we work on, and 3.0 is quietly a massive course-correction towards collaboration.
Basically, a Causality document is complex, and once multiple users edit it at the same time, if it's not done correctly, it's possible to produce gibberish data. 3.0 internally changes many things to be inherently sync-friendly.
What we want, and already have running as prototypes, is extremely real-time sync, basically <100ms sync that feels more like screen sharing, and you can be as offline or as online as you want. There's no locking and no babysitting. But this requires us to align all the data to behave in ways where you can much more just smash multiple branches of a document together and it all works out.
There would have been faster paths to sync, but they would involve compromises we found unacceptable, like locking that users have to babysit, or needing to "check in" commits. In the model you're actually getting, it's as real-time as Google Docs, but on a much more complicated document involving everybody in the same space and on the same timeline. We want to do it right so that it can handle the load of becoming a much bigger app.