The link is superficial at best and misleading at worst. For example:

Troposphere and CDK compile down to YAML and are therefore limited in what they can express. The Pulumi engine understands general-purpose language patterns, dependencies between objects, and therefore delivers a better overall experience. Pulumi also supports going beyond what you can express in YAML, such as building and publishing a Docker container image, authoring serverless functions in code, automating packaging and versioning of code, and so on.

Only someone who has never used CDK could have honestly written this. CDK can do all of this, it's not limited to YAML. Custom resources and docker bundling are a thing.

Pulumi integrates with a number of CI/CD providers and source control systems (SCMs) out of the box, for easy continuous delivery with systems you might already be using.

Although CloudFormation can be used in this manner, it requires manual configuration, and is designed to work best with AWS’s own CodeBuild/Pipeline products.

It doesn't require any manual configuration.

Pulumi integrates with your identity provider—including GitHub, GitLab, Atlassian, or any SAML/SSO 2.0 provider (such as Azure Active Directory, Google G Suite, or Okta)—for auditing and access controls using your existing enterprise systems of record. AWS CloudFormation can be manually integrated with those systems with greater effort.

How does it integrate? I can set up SSO on AWS completely as code with Pulumi?

this is referring to authentication on the state storage:

...which also requires manual integration, just like CDK.

All of the above leave a bad impression. I was hoping someone from the community would know about an independent analysis that would be frank, that's why I posted here.

Also wondering about Pulumi's answer to CDK Pipelines, which take care of pretty much everything when creating CI/CD pipelines.

@billowy-army-68599 I'd like to apologize if I came across as confrontational - that was not my intent, but I do see how my tone could have been more neutral. This was because, frankly, I took a bit of offense to the suggestion that the mentioned link can be considered in-depth, and because it's obviously biased and not factually correct. But the reason I asked the question is not to bash on Pulumi. Quite the contrary - I have a bunch of experience with CDK, but none with Pulumi, and I would love to learn it, and maybe switch to it down the line (because of multi-cloud capabilities), but I just need to understand the differences properly, without marketing pitches.