3 ms·

How does this compare to Marimo?

• jampekka 2y ago
  Doesn't seem to fix the invisible state problem that Marimo fixes.
  • set92 2y ago
    From my POV is not fixing, is another way of work. I don't like what Marimo does, because for that I have scripts. If I'm loading files from S3, I'm being charge for it. If Marimo re-executes this cell to maintain the state, it will charge me double. I don't need that. I'm able to organize my code, and know how it is being run.
    • jampekka 2y ago
      I use mostly the script workflow, but for exploration Marimo is more convenient. It got also to-disk memoization recently. Kinda best of both worlds for exploration (although I'm not a huge fan of editing code in browser). In comparison to the JupyterLab hidden state spaghetti it's a fix. With proper structuring of the blocks, Marimo will not re-execute the cell. Also memoization in script based workflows is still somewhat clunky on Python even with something like Snakemake. I do find Marimo's approach, "global" variables tracked between blocks, less than ideal, but it's the best out there.
    • amoss 2y ago
      https://docs.marimo.io/guides/expensive_notebooks/ https://docs.marimo.io/guides/expensive_notebooks/