The agents are the new browser statement is a simplification to succinctly express the UI shift from the passive interface. I do like to think it's a lot like desktop->mobile where it's a shift as much as an expansion.
Also nailed on the points about "legibility". Thanks for the contribution!
I love how it does not lock you into an agent loop. Everything's composable and you use as much or little as you need. Can't wait for the Typescript version!
I didn't find the hero video on https://runme.dev/ very helpful. I think it would be much easier to understand what Runme is for if you replaced the video with the "Make Markdowns Interactive" demos.
the best part with the Dagger + Runme combo is that it runs entirely local. this isn't just a huge with for portability. it also cuts down development cycle times significantly.
Nice! Would be lovely to have a few "workflow examples" and tutorials which really showcase the capabilities of this setup on your website, I'm not exactly sure I understand yet in what kind of cases it really shines
My company is currently adopting this and I don't see the appeal yet - likely from a lack of knowing much about it.
I added it to a side project just to get familiar and it added quite a few sdk files and folders to my project, and lots of decorators. It also required Docker and yadda yadda yadda.
I just could not justify using it compared to just running some regular Typescript file with Bun (or, in a different project, `go run cmd/ci/main.go`)
Simple problems require simple solutions. If Makefile, NPM run, or Rake gets the job done, stick with it. That's great.
The problem that Dagger and similar efforts solve is for pipelines at scale, whether that's a sea of microservices maintained by an armada of teams (which never work the same) or your massive pipelines that should be decomposed into a more atomic pipeline that fed into one.
I believe the latter is a big productivity hurdle even without org-scale. My release pipeline runs for 25min with a team <5 because it's multi-staged (testing pyramid) and includes end-to-end tests. I love my pipeline because it makes me feel safe releasing my software upon success.
However, god forbid it fails with a non-obvious error of 20 minutes into exec. Lack of portability (Hi GHA vendor lock-in) and reproducibility (local-run = impossible) will make this feedback-loop hell.
Now, wiseguys might tell me that pipelines shouldn't run for multiple minutes and only unit tests blah. That's divorced from reality. This sentiment won't not solve automation problems and won't optimize for velocity. It merely throws it over the fence to somebody else. If you have "the luxury" a QE/QA/Release team which I feel bad for.
So the question to ask yourself is: how do I know I have outgrown `go run cmd/ci/main.go`?
This Jupyter notebook-like system you're describing here is basically Runme. It do not yet have an IntelliJ/Jetbrains plugin; however, the Kernel Architecture outside of the headless CLI allows for integration into any IDE or UI.
It's all open source. Please get involved! We'd be happy to have you.
We've expanded significantly onto the idea of a toy script/utility to bring multi-modality (editor, notebook, terminal, browser) with shared sessions to what's at the core, a universal task runner (see architecture link below).
I'd love to chat about combining efforts if you love hacking on this. The same goes for the author of `mdx`.
The agents are the new browser statement is a simplification to succinctly express the UI shift from the passive interface. I do like to think it's a lot like desktop->mobile where it's a shift as much as an expansion.
Also nailed on the points about "legibility". Thanks for the contribution!