HackerTrans
トップ新着トレンドコメント過去質問紹介求人

dmadisetti

no profile record

投稿

[untitled]

1 ポイント·投稿者 dmadisetti·11 日前·0 コメント

Please Do Not Touch

readme.dm
2 ポイント·投稿者 dmadisetti·11 日前·0 コメント

GRPO vs. GDPO: Building Intuition for RL Reward Policies

huggingface.co
2 ポイント·投稿者 dmadisetti·6 か月前·1 コメント

Closer to production quality Python notebooks with `marimo check`

marimo.io
31 ポイント·投稿者 dmadisetti·9 か月前·23 コメント

コメント

dmadisetti
·6 か月前·議論
Relevant paper: https://arxiv.org/abs/2601.05242
dmadisetti
·8 か月前·議論
realtime collaboration is in under marimo experimental (just flip the flag)

marimo doesn't support creatine :)
dmadisetti
·9 か月前·議論
We've addressed this too by allowing a setup cell:

    ...

    with app.setup:
        import numpy as np
    
    @app.cell
    def cell_uses_np():
        # no np needed in signature
        result = np....
The best part about this pattern is that it enables "pure" (only dependent on setup cell) functions to be addressable:

    with app.setup:
        from typing import Optional, Any

    @app.function
    def my_fn(arg: Optional[Any]) -> Any:
        ...
but nice convergent design :) glad to see to see we're addressing pain points
dmadisetti
·9 か月前·議論
marimo has a quarto extension and a markdown fileformat [1] (marimo check works on this too!). The python fileformat was chosen such that "notebooks" are still valid python, but yes- the format itself is almost an implementation detail to most "notebook" users. Cells _are_ actually callable and importable functions though (you can give them a name), but the return signature is a bit different from what's serialized.

> The discipline of keeping cells in order may be painful, but it’s what makes the flow of analysis understandable to others.

We might have to agree to disagree here, you can still chose to have your notebook in order and something you can be disciplined about. The difference is that a marimo notebook can't become unreproducible the same way a jupyter notebook can, _because_ the order doesn't matter.

But thanks for the feedback!

[1]: https://github.com/marimo-team/quarto-marimo
dmadisetti
·9 か月前·議論
> But I really don't want to deal with yet another AI assistant, especially not a custom one when I'm already using Claude/etc from the CLI and I want those agents to help me edit the notebooks.

So funny story- you can use exactly the same CLI tools in your notebook. Zed built out the ACP spec [1] which lets Claude Code go anywhere that implements it (as of Oct 2nd; emacs, vim, zed and marimo [2])

[1]: https://github.com/agentclientprotocol/agent-client-protocol

[2]: https://zed.dev/blog/acp-progress-report
dmadisetti
·9 か月前·議論
Soft launched in pre-release, but a full version is coming!
dmadisetti
·9 か月前·議論
Arguments are typed if explicitly specified in definition, e.g.

    ```python
    @app.cell
    def my_cell():
        x : int = 1
        return (x,)

    @app.cell
    def consumer(x : int):
        y = x
        return
    ```
We've talked about building out implicit typing into our serialization- but that may be a larger can of worms.
dmadisetti
·9 か月前·議論
marimo notebooks double as python Python programs, which means they can be lint-ed like any other code. `marimo check` catches notebook-specific issues (variable redefinition across cells, circular dependencies) with Rust-inspired (and uv; uv is amazing) error messages. It outputs JSON for AI agents to self-correct, integrates into CI pipelines, and includes `--fix` flags for automatic repairs. The team is already using it in their own CI and seeing Claude Code iterate on notebooks without human intervention.
dmadisetti
·12 か月前·議論
Hey, if your name had an accent, workspace creation should have failed

Not sure how we missed that in testing. But it should be good to go now
dmadisetti
·12 か月前·議論
I just turned off /notebooks in robots.txt

Our thoughts are the same as gists- Molab is built to share your work and give you a place to tinker. Please don't put your api keys in there
dmadisetti
·12 か月前·議論
Everyone knows prod doesn't break on the weekends