3 ms·

> When working with Jupyter, too often you end up with directories strewn with spaghetti-code notebooks, counting up to Untitled12.ipynb or higher. You the note

> When working with Jupyter, too often you end up with directories strewn with spaghetti-code notebooks, counting up to Untitled12.ipynb or higher. You the notebook author don’t know what’s in these notebooks This is such a small UX thing but it’s so damn important. The simple fix is to not auto-name notebooks untitled-# when the user clicks new notebook just ask the name straight away, if they can’t name it don’t create it. It might add the smallest amount of friction to the UX, but it’s so damn important. Also the choice of json as the file format is just plain wrong. Why the project hasn’t just abandoned that entirely and done a json-#python back and forth when writing to file is beyond me. There are extensions that do this, but that’s a really clunky interface, and while I can set it up for myself it’s difficult to force upon others in a corporate environment. Great to see someone is taking the seemingly small things up, because they mean a world of difference to the overall ecosystem.

cantdutchthis 2y ago
(someone from the marimo team here) How you start the marimo notebook, via `marimo edit must-give-name-to-this-file.py` is indeed one of my teeny by favourite features of it. When you start a new notebook you're kind of forced to name it immediately.
BrenBarn 2y ago
> The simple fix is to not auto-name notebooks untitled-# when the user clicks new notebook just ask the name straight away, if they can’t name it don’t create it. The even simpler fix is to just not name them until the user does. That's the way other programs work. If you create a new document in a word processor, it will say "Untitled" at the top of the window, but it doesn't create a file called untitled.doc on disk until you do "Save as" and choose a filename. It has always irritated me that Jupyter insists on having an on-disk file right from the beginning.
janalsncm 2y ago
It would be neat if it worked similar to ChatGPT sessions which give themself a name based on the conversation. You could have a small local model that gives a default name automatically. It would also be great to have a decent search across notebooks in a project so I could quickly find an old function.

cantdutchthis 2y ago

(someone from the marimo team here) How you start the marimo notebook, via `marimo edit must-give-name-to-this-file.py` is indeed one of my teeny by favourite features of it. When you start a new notebook you're kind of forced to name it immediately.

BrenBarn 2y ago

> The simple fix is to not auto-name notebooks untitled-# when the user clicks new notebook just ask the name straight away, if they can’t name it don’t create it. The even simpler fix is to just not name them until the user does. That's the way other programs work. If you create a new document in a word processor, it will say "Untitled" at the top of the window, but it doesn't create a file called untitled.doc on disk until you do "Save as" and choose a filename. It has always irritated me that Jupyter insists on having an on-disk file right from the beginning.

janalsncm 2y ago

It would be neat if it worked similar to ChatGPT sessions which give themself a name based on the conversation. You could have a small local model that gives a default name automatically. It would also be great to have a decent search across notebooks in a project so I could quickly find an old function.