I don't understand why I would use this over aws CDK in python.

cdk is already an abstraction over the javascript cdk,

which is an abstraction over cloudformation,

which is an abstraction over the api..

I just want to navigate some of the claims made by Stelvio and others in this thread and see if maybe I'm missing something after reading the docs:

- Ship Python to AWS in minutes, not days: I can already do this with cdk? It's highly dependent on the project requirements. AWS already provides a sleuth of high level constructs with sensible defaults.

- great for really small apps where you want your resource definitions colocated with the code using them: CDK is just code? You can put it all in one place or split it into files. I don't get how this is new.

- easier to manage IAM permissions this is the bread and butter of cdk. I can simply do Resource.grantRead(lambdaFunction) without touching IAM. Who was complaining about this?

The only advantage I see here over CDK is using Pulumi as the underlying resource engine, which I admit performs better on deployment speed. But then we arrive to the question: Why not just use Pulumi, which already gives me IaC in python?