Pulumi 3.0
Glad to see all the innovation happening in the IaC space.<p>I like the multi-language premise of Pulumi but I have the feeling that over time one of the languages will gain a significant advantage over the others (better supported, more features, native...) and thus will become the primary language for Pulumi package authors and users (similar to HCL for Terraform and TypeScript for CDK).<p>Meaning that eventually all the &quot;serious&quot; Pulumi users will end up converging on one single language (similar to this comment of a CDK user migrating from Python to TypeScript). Feedback loops will only help amplify this effect (e.g. more Pulumi users on language A -&gt; more examples online -&gt; more package authors working in this language -&gt; better established best practices -&gt; more submitted issue tickets for language A -&gt; language better supported by Pulumi -&gt; more users...)<p>Curious about how Pulumi multi-language components [0] work under the hood. Isn&#x27;t writing a &quot;Pulumi schema&quot; describing resources the same as writing declarative HCL at the end of the day?<p>[0] <a href="https:&#x2F;&#x2F;www.pulumi.com&#x2F;blog&#x2F;pulumiup-pulumi-packages-multi-language-components&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.pulumi.com&#x2F;blog&#x2F;pulumiup-pulumi-packages-multi-l...</a>