Dagger: Define software delivery workflows and dev environments
1–10 of 78 posts
Re: Dagger: Define software delivery workflows and dev environments
#2Re: Dagger: Define software delivery workflows and dev environments
#3I was interested in the beginning for CI/CD, but then they tried to take a kind of "AI-oriented" view in order to ride the AI wave, and the value prop of their tool was completely muddied up...
Re: Dagger: Define software delivery workflows and dev environments
#4Then... it wasn't. The more I read the less I ever want to see this again. The LLM train has got to end at some point.
Re: Dagger: Define software delivery workflows and dev environments
#5Re: Dagger: Define software delivery workflows and dev environments
#6Re: Dagger: Define software delivery workflows and dev environments
#7This looks interesting but I’m trying to understand it in more layman’s terms. Is it more about providing abstractions for llms to work within to do things?
But, the marketing heavily focuses on LLM stuff to the point of making everyone confused.
Re: Dagger: Define software delivery workflows and dev environments
#8Without the LLM bits, this is basically like Bazel or buck2, right?
Re: Dagger: Define software delivery workflows and dev environments
#9Anybody used it? Without the LLM bits, this is basically like Bazel or buck2, right?
Re: Dagger: Define software delivery workflows and dev environments
#10I ended up opting for CUE and GitHub Actions, and I'm glad I did as it made everything much, much simpler.