thanks for the plug! i've been pushing this idea further @marimo.io. my "scratch-nb" folder is now just self-contained notebooks:

uvx marimo edit --sandbox notebook.py # like "docs.new"

which I often share as gists w/ others:

gh gist create notebook.py # publish
uvx marimo edit

ok actually this time

Observable-like cell minimap coming soon to a @marimo.io notebook near you 🫡

happy to finally share what we've been cooking 🍳

yup! or make only pip/uv all you need to run some js build system/tooling (e.g., transform some React/Svelte/Vue/TypeScript for the browser)

I’m also excited to be presenting Oxbow as part of my talk on composability at the #SciPy2025 Conference on Wednesday! Hope to see some of you there.

cfp.scipy.org/scipy2025/ta...

@marimo.io now has a tree-based UI for uv environments

add/remove/upgrade deps the uv way — no more flat pip-style lists or accidentally pip-ing your env

yah, no shade on the developers/design but this has always seemed like a huge oversight with flight to me. probably a diff evaluation of trade offs, but still

spending some time on our uv integration in @marimo.io – starting with things like this selector for package “extras”

what’s frustrated you about using packages in notebooks?

preparing for some potentially unhinged things...

have a nice budget to upgrade my at home setup. what’s one thing that ~actually~ made a difference in your space?

i believe duckdb comes from cwi in amsterdam, and (not technically db) polars from netherlands