That’s true. Kind of hard to remove something though. If you decide it was a mistake to support Python / Go / whatever later then it’s going to be a really hard to take it away from people.

Turns out this has been the source of much debate on the team. Our hope is that the community takes us where they want to go, and that this helps 1,000 flowers bloom and for us to understand better how people want to use Pulumi and where. For example, I have a suspicion that the JavaScript/TypeScript frameworks are going to gear very heavily towards serverless, and Python perhaps for lower level DevOps style packages, but we shall see. In short, agree 100% with your concerns, and we will learn a lot more here in the weeks to come. I hope it doesn't make your experience with Pulumi less awesome though 🙂 If it does, please don't hesitate to let us know. I will personally port your favorite Python package to Node.js if you ever find one that's not available -- and you can hold me to it!