Yup! Not affiliated in anyway, just a fan. I like jupyter but marimo's my go to for a few reasons:
- Automatic reactivity can be turned on (will trigger dependent cells if you uptade an upstream one)
- Much nicer non-json file format (just python files, with a seperate output)
- Much better virtual environment integration / managent (this is always a hassle with jupyter)
- Widgets are great!
- Better LLM integration (new marimo-pair means llm can inspect the actual python runtime objects)
- It generally "looks" a lot nicer if you're using the web ui, which is nice.
The cell DAG enforces that there’s no implicit state, which reduces cognitive load for me a lot and provides some pressure to abstract experimental code into functions. In Jupyter this is left to user discipline and restart-and-run-all workflow
The reactive components are also really nice for interactive plotting and exploratory data analysis. You can do this in Jupyter but it feels less seamless somehow. Interactive marimo workflow feels like streamlit but in a notebook interface
One thing I miss from Pluto.jl workflow is `let` for lowering friction for exploratory or plot cells. In marimo you have to name a `_` prefixed function and then call it which is better than nothing but not as clean as `let`. This is a minor complaint that’s more down to language features though
- Automatic reactivity can be turned on (will trigger dependent cells if you uptade an upstream one) - Much nicer non-json file format (just python files, with a seperate output) - Much better virtual environment integration / managent (this is always a hassle with jupyter) - Widgets are great! - Better LLM integration (new marimo-pair means llm can inspect the actual python runtime objects) - It generally "looks" a lot nicer if you're using the web ui, which is nice.