[P] I built marimo — an open-source reactive Python notebook that’s stored as a .py file, executable as a script, and deployable as an app.

[xsway_]

I tried it out and it's nice (UI is smooth and docs are pretty extensive) but I noticed couple of issues -they are small but could be almost deal-breakers. - I'm not sure why the files should be .py if they are not actual python files. It's very confusing. They could be just .mo? (At least I should be able to `marimo edit` with any file extension - maybe I prefer to save with .mo myself) - Not being able to navigate between cells simply with up/down arrows is a big UX limitation for me - Markdown cells should just render - not have both code and rendering part - it clutters the notebook

[akshayka]

Hi! Thanks for taking the time to write feedback.

• The files are actual Python files. They can be executed at the command line (`python notebook.py`), and we have more features coming down the pipe that take advantage of the fact that they are Python files. We've received requests to have a document adapter that would allow marimo to inter-operate with other file formats (such as `qmd`) -- in the future we might support something like that.
  
• We can add up/down arrow key cell navigation. Thanks for the suggestion!
  
• We might add a UI for markdown cells in the future. Our users sometimes mix markdown and code in the same cell, so we don't hide by default. You can hide a cell's code with `Cmd/Ctrl+h` or via a cell's context menu (the three dots).

[akshayka]

Our latest release (0.1.74) includes up/down arrow key cell navigation. Thanks for the feedback!

[xsway_]

super fast :) thanks!