Live data from Hacker News

OpenTofu Response to HashiCorp's Cease and Desist Letter

opentofu.org

11–20 of 33 posts

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#11

> “for_each” implementation for “import” blocks, Well, I'm officially on board with this project. We've been told this is impossible for years. Seems like this is pretty air tight for OpenTofu, but cease and desist letters are usually hoping to intimidate you into action anyway. edit: looks like I may have confused import blocks with provider blocks... please give me for_each support for provider blocks! please!

We are super excited to be implementing what the community has been asking about for years. It's what drives our core team.

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#13

An official apology from the author of the article that sparked the entire discussion - https://twitter.com/mjasay/status/1778454498664690108 It takes guts to publicly admit you were wrong.

Until there is an update to the original article [0], I don't find this apology particular meaningful. 0: https://www.infoworld.com/article/3714980/opentofu-may-be-sh...

It's not even been an hour...

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#14

An official apology from the author of the article that sparked the entire discussion - https://twitter.com/mjasay/status/1778454498664690108 It takes guts to publicly admit you were wrong.

Until there is an update to the original article [0], I don't find this apology particular meaningful. 0: https://www.infoworld.com/article/3714980/opentofu-may-be-sh...

You're not wrong, for sure. I hope this happens, too. But it's still more than most "experts" are capable of.

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#17

An official apology from the author of the article that sparked the entire discussion - https://twitter.com/mjasay/status/1778454498664690108 It takes guts to publicly admit you were wrong.

It does take guts to admit you were wrong. He didn’t though.

This is a non-apology, “apology”.

He says he was wrong about being so “strong.” Wtf? That’s not an apology at all.

His “analysis” was complete bullshit. Hilariously, in his “apology” he says “a few minutes of LGTM isn’t enough.” Then he adds a kind of “trust me bro” tidbit to counter the people that called him out for his few minutes of garbage analysis.

If he had anything ACTUALLY damning, he would have put it in the article. Instead he put the most vaguely related stuff and said “see! Smoking gun!”

This guy has credentials that make it obvious he should know better. Yet he’s still basically saying he was only wrong in tone.

I don’t get his motive. Is he personally involved with Hashicorp or something? Is he friends with an executive? It doesn’t make sense to me at all, unless there’s some other motive he’s not talking about.

He tried to make it sound like “I have an honest concern.” To me it just sounds like it could very well be a stealth PR campaign from some Hashicorp lawyer that backfired immediately. Reminds me of the crap they pull in the entertainment industry.

That’s my rant. These opinions are my own, yada yada.

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#18

Hah! I knew that previous article smelled like a poorly researched hit piece on OpenTofu!

Smells like stinky tofu (臭豆腐)

heh, clever pun. but hardly. have you tried it? stinky tofu doesn't smell as bad as its reputation. and it tastes great. stinky tofu doesn't hold a candle to durian or some of the more pungent cheeses. of course this comment is coming from a guy who likes those cheeses, and durian, so YMMV. my biggest gripe about stinky tofu is that it isn't stinky enough.

Re: OpenTofu Response to HashiCorp's Cease and Desist Letter

#19

An official apology from the author of the article that sparked the entire discussion - https://twitter.com/mjasay/status/1778454498664690108 It takes guts to publicly admit you were wrong.

Until there is an update to the original article [0], I don't find this apology particular meaningful. 0: https://www.infoworld.com/article/3714980/opentofu-may-be-sh...

For me the smelliest part of this is the timestamps. The C&D is dated April 3. The InfoWorld article is timestamped 8:49 AM PDT, the same day, and the files called out in both places are the exact same five. There is no way I can see that the article wasn't just a rehash of a draft C&D provided to Matt Asay before it was even delivered to the OpenTofu project, and without either HashiCorp or Asay giving OpenTofu a chance to respond. Even if the C&D were 100% justified (and it's clearly not), that is extremely dirty pool.
Post reply on HN