I'll be there too! Giving a talk on how @marimo.io notebooks are formed, using the AST of user code.

Thanks @paddymullen.bsky.social for helping make marimo better with all your feedback! 🙏

marimo is free and open source: github.com/marimo-team/....

Please give it a try — we appreciate any and all feedback!

This blog post is the second in a series that goes deep into why we think the Python notebook needs reinventing and what we're doing about it.

The first post, in case you missed it: marimo.io/blog/lessons...

Treating notebooks as code makes them more reproducible, portable, and interoperable — enabling many use cases that were previously out of reach for notebooks.

Our file format lets us make use of Python standards like inline script metadata, enabling tight integration with uv for reproducibility down to the packages.

marimo stores notebooks as plaintext Python files, with each cell represented as a function.

This makes notebooks git-friendly and importable as modules, while also supporting execution as a script and many other things.

Jupyter notebooks are what Pydantic creator calls "horrid blobs": JSON that can't be versioned with git or treated as software.

Our blog explains how @marimo.io fixes this problem.

We also have an accompanying video by
@koaning.bsky.social!

www.youtube.com/watch?v=skuI...

"Jupyter-style notebooks are a good example of a deep architectural mistake that needs hacks on hacks to remain barely serviceable.

Luckily there are new approaches, e.g. marimo and
Pluto, that don't have the same root issue"

"Stop using Jupyter and switch to marimo"

blog.mdfranz.com/threat-hunte...

"Just try marimo."

www.reddit.com/r/Python/com...