3 ms·

It's hard for me to imagine the use case where this is appropriate. I have looked at marimo several times, and while it's great for interactive computing, and

It's hard for me to imagine the use case where this is appropriate. I have looked at marimo several times, and while it's great for interactive computing, and it has a fantastic team, it's not a replacement for notebooks and I find their use of the term "notebook" confusing. As a scientist, I don't understand what use case they are exploring, but I do know it's not the use case where Jupyter was created and it's not my current use case for Jupyter on teams I work with.

abdullahkhalids 2y ago
If you read what they think the problems to solve are, you will get it. small edits to code yield enormous Git diffs; code is copy-pasted across notebooks, instead of reused; magic commands limit the portability of notebook code; logic that would be useful as a script or library gets thrown away; logic that should be tested almost never is. These are problems primarily a software engineer has. Not problems a scientist thinks are important. If you asked a scientist to list problems with Jupyter notebooks (and there are many), it would be very different list, primarily about science.
- akshayka 2y ago
  Yea. This blog post is definitely written for software-minded people who work with data. We do have another post that explains some of the problems that marimo hopes to solve for scientists, chief among them computational reproducibility and publishing interactive science communications on the web: https://marimo.io/blog/slac-marimo https://marimo.io/blog/slac-marimo