|
|
|
|
|
by randomtechguy
451 days ago
|
|
It's a fair point - My opinions and use case are my own, I didn't mean to imply or assume there were promises not kept. The dagger team has been nothing but supportive and I do think has built a great community. That said, in the early days it was definitely pitched for CI/CD - and this how we've implemented it. > What is it?
> Programmable: develop your CI/CD pipelines as code, in the same programming language as your application. > Who is it for?
> A developer wishing your CI pipelines were code instead of YAML https://github.com/dagger/dagger/blob/0620b658242fdf62c872c6... Edit: This functionality/interaction with the dagger engine still exists today, and is what we rely on. The original comment is more of an observation on the new directions the project has taken since then. |
|
I just wanted to clarify that in terms of product design and engineering, there is unwavering focus and continuity. Everything we build is carefully designed to fit with the rest. We are emphatically not throwing unrelated products at the wall to see what sticks.
For example, I saw your comment elsewhere about the LLM type not belonging in the core. That's a legitimate concern that we debated ourselves. In the end we think there is a good design reason to make it core; we may be wrong, but the point is that we take those kinds of design decisions seriously and we take all use cases into account when we make them.