I'm debating now between myself and myself which SDK to use, what are the tradeoffs, what should I consider when making this decision.
I appreciate any help you can provide.
#Comparison of SDKs in the Docs
dense socket
copper stag
I would personally pick what would be most accepted by a team or organisation. most familiar language. pretty sure the aim is that any sdk can achieve the same with an exception of some languages have some features while others do not and I think the dagger team does try to utilise a bit there. I'm not on the team just giving my perspective as a user so far. I'm a c# dev for 12+ years. I went with go instead of the typescript one because I was bored of typescript and so many new cloud based products and cli tools are written in go. so I went with go ( my though it also that dagger is go and so maaaaybe the go sdk probably has the best dx but it'd a bias opinion I could be wrong there )
arctic brook
Hey, every SDK shares the same API so you can obtain the same result with Go, Typescript or Python (we also got Elixir and Rust but they're maintained by contributors).
Usually, people picks the SDK based on which language they are using in the project, if you're building a Go app, then go for Go, if you're in Typescript, then TS etc..
If you're building a soft in a language not implemented by Dagger, I would say that it depends on the question: "What language is the most comfortable for you and your team?"
You can looks for a specific feature of one language that you would like to us for your CI.
However, keep in mind that the Dagger API is the same in every languages (the only difference is that Go supports interfaces but we're working on that on TypeScript and Python).
So you're experience with the Dagger API shouldn't change that much no matter the language.
The only true difference between SDK is the performances, the Go SDK will be the fastest, then Python and Typescript is the slowest. But again, we're actively working on this too so no matter the SDK, you'll have the same dev experience 😉
copper stag
is the .net sdk still on the table or community driven? I see some others which you didn't list in the sdk folder in github