18 ms·

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 mi

by delano 2y ago

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.

samuelstros 2y ago
here, be blown away https://github.com/opral/monorepo/tree/main/lix https://github.com/opral/monorepo/tree/main/lix 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
- TheBengaluruGuy 2y ago
  this is quite interesting. I'll surely keep it in mind while we build out deeper collaborative features.!
- delano 2y ago
  Wow, yeah. "Bringing backend features to files." This feels a bit like that time we saw Etherpad playback for the first time. I'm just not sure if I've grokked the big picture yet. https://news.ycombinator.com/item?id=495336 https://news.ycombinator.com/item?id=495336
  - samuelstros 2y ago
    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.
mcintyre1994 2y ago
You might also like Elixir Livebook! :) https://livebook.dev/ https://livebook.dev/
TheBengaluruGuy 2y ago
Thanks for your feedback. > as a file that can be version controlled 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.

by delano 2y ago

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.

samuelstros 2y ago

here, be blown away https://github.com/opral/monorepo/tree/main/lix https://github.com/opral/monorepo/tree/main/lix 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

TheBengaluruGuy 2y ago
this is quite interesting. I'll surely keep it in mind while we build out deeper collaborative features.!
delano 2y ago
Wow, yeah. "Bringing backend features to files." This feels a bit like that time we saw Etherpad playback for the first time. I'm just not sure if I've grokked the big picture yet. https://news.ycombinator.com/item?id=495336 https://news.ycombinator.com/item?id=495336
- samuelstros 2y ago
  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.

mcintyre1994 2y ago

You might also like Elixir Livebook! :) https://livebook.dev/ https://livebook.dev/

TheBengaluruGuy 2y ago

Thanks for your feedback. > as a file that can be version controlled 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.