3 ms·
They have SDKs in many languages, not just Go. I use the python one. And they use code, not a DSL.
by esafak 11mo ago
They have SDKs in many languages, not just Go. I use the python one. And they use code, not a DSL.
- stephen 11mo agoRight, my point is that this: https://docs.dagger.io/cookbook/services?sdk=typescript https://docs.dagger.io/cookbook/services?sdk=typescript Still looks like "a circa-2000s Java builder API" and doesn't look like pleasant / declarative / idiomatic TypeScript, which is what aws-cdk pulled off. Genuinely impressively (imo), aws-cdk intermixes "it's declarative" (you're setting up your desired state) but also "it's code" (you can use all the usual abstractions) in a way that is pretty great & unique.
- shykes 11mo agoCould you share an example of aws-cdk code that you think Dagger should take inspiration from? Dagger and aws-cdk work very differently under the hood, so it's difficult to make an apples-to-apples comparison. If there's a way to make Dagger more TS-native without sacrificing other important properties of Dagger, I'm interested. Thanks.
- stephen 11mo agoHello! Yeah, I totally get Dagger is more "hey client please create a DAG via RPC calls", but just making something up in 30 seconds, like this is what I had in mind: https://gist.github.com/stephenh/8c7823229dfffc0347c2e94a3c99227b https://gist.github.com/stephenh/8c7823229dfffc0347c2e94a3c9... Like I'm still building a DAG, but by creating objects with "kinda POJOs" (doesn't have to be literally POJOs) and then stitching them together, like the outputs of 1 construct (the build) can be used as inputs to the other constructs (tests & container).