is dagger run the "old" way?

[minor tiger]

Hi! good question, let me give you a quick answer on this thread

1. You can still embed Dagger calls in a tool running on your host machine, like you've already been doing. So that code, and the dagger run wrapper to call it, will continue to work.

2. That said, we think writing custom client tools will become a less common use case, because most of the time it's easier to write a Dagger Function and call it directly with dagger call. Having to maintain a custom CLI for your project CI is overkill most of the time.

3. We need to better document these facts, it's planned, but we had to cut a few corners to get to launch. There is a lot more documentation coming.

[buoyant sparrow]

Alright, that makes sense, thank you for the explanation.

[lunar latch]

I love that this also enables/encourages dagger as a general entry point task runner. This to me is an exciting use case in addition to CI, eliminating additional task runner tooling (Makefile, mage, just, etc.). Is that daggerizing too far? - definitely not:)