[nuker]

> Doing the same infra, across multiple clouds, is a different thing, it's not a Hashi thing.

Not sure about this. Here is what official site says:

"Provisioning infrastructure across multiple clouds increases fault tolerance, allowing for more graceful recovery from cloud provider outages."

https://www.terraform.io/use-cases/multi-cloud-deployment

[kkapelon]

Terraform supports different clouds but with completely different syntax. The marketing on the website just informs you what you can use any cloud you want. The message is against other tools such as cloud formation (AWS only) or GCM (Google only), ARM (Azure only) and so on.

To give you an analogy it would be like Firefox saying that they are "multi-OS" meaning that you can install Firefox if you have Windows and you can install Firefox if you have Linux. It doesn't mean that you must/should have Linux and Windows at the same time as a user.

[jen20]

Strictly incorrect. The syntax is the same for every cloud - either HCL2 or JSON. What you are calling syntax is actually the resource model. Every project which claims to bridge this resource model ends up implementing a lowest common denominator time sink which doesn’t stand up to basic scrutiny.

Your analogy also does not demonstrate whatever it is you seem to think it does - Firefox is indeed multi-OS.

[kkapelon]

It is ok. Parent already said that that they mean something different with "multi-cloud" https://news.ycombinator.com/item?id=38649796

[jen20]

The definition of multi-cloud does not matter when talking about what syntax is.

[nuker]

> The marketing on the website just informs you what you can use any cloud you want.

Disagree. The message says “fault tolerance”, meaning you deploy same things in different clouds. Which brings back to my original post - TF does not help with this, as jen20 said - very different resource models.