> The thing that makes the difference is what is running on people's laptops, because that's what people will eventually put into prod.

"It works on my machine!"

"Then we'll ship your machine"

Docker: https://miro.medium.com/v2/resize:fit:720/format:webp/1*Ibnw...

Lol plain old VMs have been shipping your machine since well before Docker was around.

And in some cases, unfortunate git commands will ship your machine too!

That works while OpenTofu and Terraform files are compatible - but once they no longer are, presumably you'd have to standardise on one or the other.

The point is that once they are no longer compatible, people would standardize on the one that they're familiar with which is most likely the one that's running on their machine.

There are enough pretty annoying and long standing terraform issues that if opentofu started picking them off I'd consider switching.

You can kinda see this with vim and neovim where both are continuing to exist and benefit each other.

Encrypted state files are either done or coming soon. That's going to be a big one, since Hashicorp used that as a selling point for Terraform Cloud.

But currently, people are equally comfortable with both; the CLI commands are exactly identical between the two, save for the name of the binary itself. In any org where both are in use, if people are forced to choose at some point, they will have to balance many other factors besides familiarity, such as features and confidence in the platform.

> The thing that makes the difference is what is running on people's laptops, because that's what people will eventually put into prod.

I disagree—I think support of deployment tooling (like Atlantis) is the bigger proof. If you are running terraform on your local machine it is likely a very small company.