I m going to be trying to sell Dagger

[frank cradle]

Hey sorry missed this message until now.

Cross-language interop in general works already, but we've only updated the Go and Python SDKs in our dev branches so far. However, we a while back did a quick POC of typescript support, so we're confident that'll work just fine too. We also intend to update the rest of the SDKs too, e.g. have discussed what Rust support would look like (though haven't tried it yet).

One thing I'm curious about though is whether Typescript would work for you or if you need plain Javascript support specifically.

Asking because everything we're doing relies on there being actual types to convert into underlying graphql APIs, so while typescript it pretty obvious, plain JS is somewhat less so. There's options in terms of JSDoc comments, which essentially give type hints for JS afaik, but overall typescript is probably a better fit if it works for your use case.

cc @lean timber

[inner eagle]

I think we will mostly be Go, and then some Python, probably JS in one or two places if they don't want to use anything else. There is a natrual tendency to match the dagger code to the primary code of the project

I'm mostly just looking for a very rough estimate / talking point

[frank cradle]

Current timeline is we're aiming for a release in November, which would include at minimum Go/Python/Typescript, but we'll also be staging this out before then as part of our normal release cycle, just with everything hidden behind experimental flags.

Is that granular enough detail to be helpful?

[inner eagle]

yeah, that's more than enough, thanks @frank cradle