| gather | TypeCell | |
|---|---|---|
| 1 | 2 | |
| 526 | 376 | |
| 0.4% | 4.3% | |
| 0.0 | 4.5 | |
| 8 months ago | 6 days ago | |
| Jupyter Notebook | TypeScript | |
| MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gather
-
Show HN: Marimo – an open-source reactive notebook for Python
You're probably referring to nbgather (https://github.com/microsoft/gather), which shipped with VSCode for a while.
nbgather used static slicing to get all the code necessary to reconstruct some cell. I actually worked with Andrew Head (original nbgather author) and Shreya Shankar to implement something similar in ipyflow (but with dynamic slicing and a not-as-nice interface): https://github.com/ipyflow/ipyflow?tab=readme-ov-file#state-...
I have no doubt something like this will make its way into marimo's roadmap at some point :)
TypeCell
-
Show HN: Marimo – an open-source reactive notebook for Python
Congrats OP on launching this, looking forward to dive further in! It's great to see people experimenting in the Reactive + Live Programming space as like you mention, I think it can bring a lot of improvements to how we build software. Did you run into any limitations adopting this model?
> A killer feature of Observable notebooks for me is that they provide the shortest possible route from having an idea to having a public URL with a tool that I can bookmark and use later
Thanks for sharing simon! I'm working on an Open Source Notion + Observable combination (https://www.typecell.org), where documents seamlessly mix with code, and can mix with an AI layer (e.g.: https://twitter.com/YousefED/status/1710210240929538447)
The code you write is pure Typescript (instead of sth custom like ObservableJS) which opens more paths to interoperability (aside from having a public URL). For example, I'm now working to make the code instantly exportable so you can mix it directly into existing codebases (or deploy on your own hosting / Vercel / whatever you prefer).
-
Local-first software: You own your data, in spite of the cloud (2019)
Thanks, great feedback!
Although it's entirely architected on a local-first stack, I indeed haven't shipped the main benefit of this, a locally installable app. There's a WIP PR here that adds PWA support: https://github.com/TypeCellOS/TypeCell/pull/352. I'll highlight this more when this is merged.
Nevertheless, some of the benefits are already noticeable and come "out of the box" with building on a local first architecture, even if not shipping an executable yet:
What are some alternatives?
vscode-reactive-jupyter - A simple Reactive Python Extension for Visual Studio Code
corrosion - Gossip-based service discovery (and more) for large distributed systems.
mermaid - Generation of diagrams like flowcharts or sequence diagrams from text in a similar manner as markdown
evolu - Local-first platform designed for privacy, ease of use, and no vendor lock-in
jupyter-vim-binding - Jupyter meets Vim. Vimmer will fall in love.
socket - A cross-platform runtime for Web developers to build desktop & mobile apps for any OS using any frontend library.
ipyflow - A reactive Python kernel for Jupyter notebooks.
mps3 - Infraless Database over any s3 storage API.