HashiCorp does not have the capacity to maintain the ecosystem on their own. In fact, Terraform is kinda stuck for years, because only a handful of people work

HashiCorp does not have the capacity to maintain the ecosystem on their own. In fact, Terraform is kinda stuck for years, because only a handful of people work on it - others are too busy maintaining AWS, Google, and Azure providers - I believe companies pay them to do so. You could look at the years-old issue about having dynamic providers or changing the syntax of count - years of discussions, tons of developers complaining about it, and nothing except lame excuses that it's hard to implement those or that the lead is not accepting anybody else's vision. Anyway, nobody will use Terraform if it only supports the 3 major cloud providers! The beauty comes with the GitHub provider, maintained by GitHub, with the PostgreSQL and RabbitMQ providers, maintained by a solo developer, the MySQL, Cloudflare, Opsgenie, Pagerduty, and tons of others, not touched by HashiCorp. Those third parties do this, because of the open nature of Terraform. Now that HashiCorp is changing its model, because it's unable to sustain its business due to its high TFC pricing that doesn't even support its own CDKTF, I suspect a fork may happen, or Terraform itself could be reimplemented with better core than the current one, which is maintained by a couple of developers. Terraform is a huge missed potential and it has so many limitations like not being able to use variables in a bunch of places, the orchestration with depends_on being so limited, the unstable chaining of resource outputs to provider configuration, etc.