Which SDK should we support next?

[shykes]

With the imminent release of the Dagger Go SDK, you can now use Dagger to program your CI/CD pipelines in two different languages: Go and CUE.

But why stop there? We plan on adding support for many other languages. Our goal is that, no matter what language you want to use to develop your CI/CD pipelines, Dagger has a SDK for it.

Of course, releasing a new SDK is work, so we need to prioritize. To help us prioritize, please 1) vote for which SDK we should support next, and 2) share details on your use case if you can!

If you want to be notified when your SDK is available, you can also fill this form and share more details about your use case.

Thank you all!

[maxdeviant]

I'm looking to use Dagger in our work monorepo. It's all TypeScript using Rush with pnpm, so a Dagger Node SDK would be the perfect fit.

We'd be using Dagger for CI and perhaps even bring it into our deployment pipelines as well 🙂

[tulis]

A dotnet SDK support would be nice 🙏

[cdhunt]

Dotnet could be built upon for Powershell as well.

[cdhunt]

https://github.com/cdhunt/dagger/tree/sdk/powershell/sdk/powershell

[kstkrv]

I guess Python, Powershell and Bash are the most popular languages among people used to write CI/CD pipelines

[Alvise88]

A PureScript support should be great!!!

[luolong]

I'd go for TypeScript language next.
Targeting both Node and Deno runtimes.

[MrChrisRodriguez]

What's your priority?

• empower people that already write pipelines with better tooling?
• enable people that don't yet write pipelines but could / should?

If it's the former, then what @kstkrv is right: go to what's already popular. If it's the latter, then JS/TS is the obvious choice. Really comes down to who you're targeting and to what end.

[MrChrisRodriguez]

Awesome! Do you have any semblance of a timeframe for Node TS/JS (understanding that deadlines slip, etc.)?

[luolong]

@jpadams I really hope that the TypeScript backend is capable working with both, NodeJS and Deno backends.

[shykes]

Awesome! Do you have any semblance of a timeframe for Node TS/JS (understanding that deadlines slip, etc.)?

It’s a matter of days 😇

[shykes]

@jpadams I really hope that the TypeScript backend is capable working with both, NodeJS and Deno backends.

We’re focusing on NodeJS first, but would love to add support for Deno. In your experience is that a lot of work? Does it require maintaining two different libraries?

[luolong]

I haven't really done any cross framework library work so far and I've only written few small utilities and apps in Deno so far, so I can't speak too much about the fundamental differences between the two, but my impression has been that generally, Deno is less encumbered with the kind of cruft that has been accumulated with Node.

My impression is that writing code in Deno tends to lean towards writing simply vanilla(ish) TypeScript, while there are definite Node'isms when developing things for Node.

Of course there are Deno and Node specific APIs that are available on one platform but not the other, but barring those, a Deno library might be quite easy to import into Node app, wile importing Node library into Deno app requires some extra effort.

Take it with a grain of salt ... I am only an occasional dabbler in the dark arts of JavaScript/TypeScript development.

[d3rp3tt3]

We need a new poll or to update this one since the team has already publicly delivered on several and launched the GraphQL API (this is the API that drives the language-specific SDKs).

Docs

• Node.js / Typescript / Javascript
• Python
• CLI
• GraphQL API

I vote for Rust next. (And I did vote for it.) PowerShell would be compelling as well. The CLI implementation can be used to create a bash script, but having a full Powershell module could unlock a bunch of compelling workflows.

[sheldonhull]

Didn't see dotnet (C#) added there. Thought might be worth mentioning c# despite my love for PowerShell. 😀

[wingyplus]

I vote for haskell and another beam languages (erlang, gleam) and zig

[humrochagf]

Dotnet core / C# would be nice, it's cross platform now and has a great entry point for corporate.
For example on my personal projects I go always with Python but at work the stack and most of the teams are C# first, and having it as an option helps a lot in the adoption.

[wingyplus]

I see that dotnet sdk already import to repository as a experimental sdk. But I'm not sure about the state of the sdk. @nabsul may answer better than me. :)

Ref: https://github.com/dagger/dagger/tree/main/sdk/dotnet

[humrochagf]

Are you writing your automation with Nuke or equivalent automation framework?

Depends, some are full gitlab-ci + docker, other pipelines use custom C# automation solution, others teamcity 🙂

[humrochagf]

I see that dotnet sdk already import to repository as a experimental sdk. But I'm not sure about the state of the sdk. @nabsul may answer better than me. :)

Ref: https://github.com/dagger/dagger/tree/main/sdk/dotnet

Nice, I'll give it a try 🙂

[nabsul]

Hi, the .NET SDK is not complete. It has a couple of proof-of-concept examples/ideas, and the beginnings of a GraphQL client code generator. It is not yet usable. I'm not sure when I'll have time to continue work on this, but the project is open to contribution as well :-)

[edumserrano]

I also think having .NET SDK support would be great!

[zeroware]

Hello, I started working on a PHP SDK. I will try to publish something if there's interest.

[zeroware]

Published the first version here : https://github.com/the-diamond-dogs/dagger-php-sdk

[rechc]

I come from Jenkins pipelines which written in groovy. I also use maven and write some extended maven goals written in groovy. So I prefer groovy or Java as next supported SDK.

[wingyplus]

You can check it out at https://github.com/dagger/dagger/tree/main/sdk/java

[beingminimal]

@shykes i think we should work on jsr.io support to make dagger js sdk available for any js runtime like deno and others.
Please have a look. Thanks