3 ms·
I find it so weird to see Jupyter being the "traditional" option in this discussion. Kudos for the shout out to excel being the main "notebook" most people hav
by taeric 2y ago
I find it so weird to see Jupyter being the "traditional" option in this discussion.
Kudos for the shout out to excel being the main "notebook" most people have experience with.
I question the choice of Python as the format. Agreed that Json is terrible. But Python will have similar problems. And a notebook is a marked up document. Using a markup language is a natural choice. Delimit areas of particular syntax and you are off to the races. (Yes, I am fond of org mode.)
- akshayka 2y agoWe're adding support markdown with fenced code blocks, which maybe gets you closer to "delimiting areas of particular syntax": https://github.com/marimo-team/marimo/pull/1332 https://github.com/marimo-team/marimo/pull/1332. Python is nice because it enables composition and reuse as vanilla scripts. But there are definitely tradeoffs.
- taeric 2y agoYes, fenced blocks is what I meant. Recreating parts of xml and cdata seems the common end goal. I think we have enough modern processing that you can do looser grammars. Composition is an odd goal to me. Most notebook usage is exploratory. As such, taking effort to reuse notebooks feels counter to the benefits of doing it again that you can get. Though, I'm a fan of seeing different workflows. And excited to be shown places I'm wrong! Kudos!