by arjxn-py on 10/24/25, 4:13 AM with 28 comments
by niam on 10/24/25, 12:20 PM
I do yearn for a day though when we're using something like Marimo over Jupyter as a default for these kinds of things. Particularly in GIS where there's more utility in being able to use a notebook-like interface for an executable routine (rather than an analysis or experiment, which is (and should probably remain) the primary use case for Jupyter).
by boxerab on 10/24/25, 2:58 PM
by anentropic on 10/24/25, 11:35 AM
by driggs on 10/24/25, 2:29 PM
> Available tools include:
> Buffer, Convex Hull, Dissolve, Bounding Boxes, Centroid, Concave Hull
Why would they want to calculate these from WASM in the browser instead of calling out to the Python kernel?
by Stevvo on 10/24/25, 10:55 AM
by arjxn-py on 10/24/25, 6:44 AM
by erremerre on 10/24/25, 9:56 AM
by tasuki on 10/24/25, 9:18 AM
What does this mean? How is it collaborative in real-time? (I don't even know how Jupyter is collaborative... as in, several people can open a Jupyter Notebook and make changes simultaneously, and things don't break for either of them?)
by rossant on 10/24/25, 6:08 AM
by TheChaplain on 10/24/25, 6:16 AM