I think they replied to that on some occasions already [0], that projects in future will diverge, especially if the community will raise issues that require that.
BUT... 1.6 was a drop-in replacement for terraform. I can see 1.7/1.8 has some new things going on, but they made effort to handle that. For instance, some new features will be available if you use .tofu extension, but not when using .tf file extension. Tofu uses .tofu one and ignores .tf if both are present.
There seems to be a clear effort to keep our code compatible with both tools (with cosmetic changes at best) for as long as possible.
We are maintaining reasonable compatibility where we can. For example, there are some terraform cloud specific features that don't make sense for OpenTofu which we have not added.
Given that we are trying to make the migration as painless as possible, we plan on continuing this approach as long as we reasonably can.
While a lot of our focus is on maintaining compatibility with new terraform releases, we also try to dedicate a lot of our release cycle to implementing features that the community is advocating for. I'm quite proud that this release is a good example of that.
We've added support for the .tofu extension and are working on IDE support for it. This will allow module authors to include support for new OpenTofu (and Terraform) features side-by-side. We have some good examples in the blog post!
In the mean time, OpenTofu is aiming to implement many of the new features that Terraform has been adding (driven by community input). We've also seen recent Terraform releases add features that OpenTofu has already included (templatestring for example).
That hasn't really changed though. He's just decided to manifest "Twitter is a video platform" into existence. The controls are still total ass though.
Yes just to be pedantic, twitter has never been "a video platform" – but that they've had support for streaming live events for years.
So take with that whatever it means, that it's just not going to be as first-class citizen like in Youtube. But the CDN etc must be good enough as those things are easier to do nowadays.
They did that for IFT-2 and the first channel I went to was one of those crypto bullshit things too. Very dumb decision on SpaceX's (well probably Musk himself) part.
YouTube does a bad job of real time takedowns of spoofed live streams. You’d think for big events like this they would have somebody just standing by and monitoring social stuff so that things like this don’t happen.
Then again you'd think one of Amazon's 1.5M employees would have the job of finding fake USB sticks for sale on the site, but apparently nobody has that title either.
> The biggest change is the updated S3 state backend which now uses the v2 Go AWS SDK underneath.
Can you shine some light on whether this change was done to maintain feature parity with Terraform's code that is also evolving? Or is this a completely new thing available only in OpenTofu but not available in Terraform?
For this upcoming release we are trying to keep feature parity where possible. This is a feature that is generally available in Terraform and has an api that is almost the same.
One significant note is that by default OpenTofu supports most s3 compatible endpoints out of the box, without having to disable s3 checksum validation (as opposed to Terraform 1.6.3).
Also our backwards compatibility with older endpoint configurations is fully supported, without any configuration changes. Terraform (as of 1.6.3) still does not function correctly with bare endpoints.
We just pushed our latest release with some pretty massive features that have been long requested!
Provider for_each allows significant de-duplication of providers and modules.
We also added the `-exclude` flag as the inverse of `-target` which the community has been waiting a long time for.
This is in addition to many other features and bug fixes. I hope you give it at try!