3 ms·
> TL;DR having options is good strategy, OpenTofu is your insurance policy and competition makes things great. I hope that includes competition beyond dotTF (a
by verdverm 3y ago
> TL;DR having options is good strategy, OpenTofu is your insurance policy and competition makes things great.
I hope that includes competition beyond dotTF (as a term to capture both TF & Tofu)?
For example, I'm keen to see what can be built in this space on top of CUE
I have concerns that this movement will fracture the ecosystem. They speak of backwards compatibility, which to me means they are going to be allowing things that TF will not understand. The paths this could take will be interesting to watch unfold, it could be a complete bifurcation or something like the NPM v Deno v Bun situation, where it seems there will be long-term convergence of the module system, but requires more work for all vendors and module authors.
re: the quote, I don't really feel an urgency to get insurance or invest in a migration just because Hashi changed their license. This seems more like a group policy for the SaaS's that are impacted than for the users of TF who aren't
---
edit, after reading the whole thing, I'm not really sure what to make of this writing, it meanders and spends a lot of time self glorifying...