If it works like Jupyter, as a file that can be version controlled, and like Deepnote where multiple people can be viewing/working on it at the same time, my mind would be blown.
solving version control for files like jupyter notebooks brings collaboration to those files without the need to give up files in favor of the cloud. playbooks could leverage lix in 1-2 years to build a file-based version of their tool
big picture is that cloud-based apps/saas is getting disrupted.
there is no value in a cloud-based solution that locks users and customers in if collaboration can be solved in the data (file) level. turns out that version control solves collaboration on the data level and is awesome to build apps.
PlayBooks are created using a UI and all state changes are tracked but we currently don't support moving back to a previous version of the PlayBook.
> where multiple people can be viewing/working on it at the same time
This is currently picked wherein we will be creating sessions for each time PlayBooks are run and sessions will have the data persistent in each cell for everyone with the link to see.
