Live data from Hacker News

Show HN: Marimo – an open-source reactive notebook for Python

github.com

101–110 of 110 posts

Re: Show HN: Marimo – an open-source reactive notebook for Python

#102
post #101

Marimo looks and feels great! Have you considered adding support for mermaid.js in the markdown? I tried including some mermaid.js in a `mo.md` invocation, but it didn't render the diagram :-) https://mermaid.js.org/

We’ve been thinking about it (but had no requests for it yet). I will look into adding it this week. If you would want to make the contribution, feel free to jump/chat in the discord.

Re: Show HN: Marimo – an open-source reactive notebook for Python

#103
post #95
post #94

Defining the same variable more than once is an error. The reason for this is obvious. But if the variable is never used in a cell that does not first write to it, reusing variable name should be possible. Allowing that would be good, because many notebook cells start with "fig, ax = plt.subplots(2, 2)" and this is currently not allowed more than once.

Does the local underscore variables feature solve this? Or the approach outlined in the plots tutorial? IMO, not allowing redeclaration is more valuable than supporting this use case. A slight paradigm shift away from your example gives you the significant benefits of a reactive environment with fewer edge cases/quirks. I'd much rather have a notebook error out instead of silently overwriting a value. You save so muc…

Yes, but what I proposed seems like no risk of silently overwriting? If there are dependencies between cells there will still be an error

Re: Show HN: Marimo – an open-source reactive notebook for Python

#104
Do you guys have anything resembling RStudio-style doc-aware code completion? [1]

I swear it's the bane of my existence whenever doing anything inside Jupyter. Coming from RStudio it always feels like operating in a vacuum.

[1] https://rstudioblog.files.wordpress.com/2015/02/s3.png

Re: Show HN: Marimo – an open-source reactive notebook for Python

#105

Do you guys have anything resembling RStudio-style doc-aware code completion? [1] I swear it's the bane of my existence whenever doing anything inside Jupyter. Coming from RStudio it always feels like operating in a vacuum. [1] https://rstudioblog.files.wordpress.com/2015/02/s3.png

Yes, we do!

Re: Show HN: Marimo – an open-source reactive notebook for Python

#106
post #7

That's one interesting project. As someone who relies heavily on collaboration with people using Jupyter Notebook. The most annoying points about reproducing their work are the environment and the hidden state of Jupyter Notebooks. This does to address directly the second problem. It does however by sacrificing flexibility. I might need to change a cell just to test a new thing (without affecting the other cells) but…

You should try pip-tools.

Re: Show HN: Marimo – an open-source reactive notebook for Python

#107
At first I thought that in effect, this project only removes a couple of Ctrl+Enter keystrokes in Jupyter-notebook workflow. But after trying out the intro I think it looks good, I really like the simple convert to a webapp.

I wonder if the state/data in the generated app are stored server-side of sent to browser.

I went through the slider example in the intro and I noticed that when I change the icon, the slider position goes back to 1. I tried to fix it so that the slider-selected value is preserved over icon changes, but didn't manage, it doesn't seem straightforward.

Re: Show HN: Marimo – an open-source reactive notebook for Python

#110
post #89

Aren't many of the issues with Jupyter being mentioned in this thread solved by Quarto? I have been advocating for it's use more at work, and NIH has even started offering classes on it through the NIH library.

Exactly my thoughts too, especially regarding reproducibility issues Quarto has been great in the past for projects at my workplace.

I have yet to try Marimo but synchronised code cells are what seems to set it apart. Quarto + jupyter-cache [1] was the closest I have managed to get to that experience but that approach has its constraints.

[1]: https://github.com/executablebooks/jupyter-cache

Post reply on HN