Live data from Hacker News

OpenTofu may be showing us the wrong way to fork

infoworld.com

1–10 of 37 posts

Re: OpenTofu may be showing us the wrong way to fork

#3

Beyond the license issue, the promised features vs. difficulty of implementing them is a knife in the 'if you don't like it, it's open source -- you can do anything you want'. It's a technically correct statement. But that is all it is.

Technically correct is the best kind of correct (tm)

Re: OpenTofu may be showing us the wrong way to fork

#5
post #4

no diff referenced, incompetency or pr campaing from hc

There are links to 3 files in both opentofu and hashicorp.

You could get the diff yourself from that. The point about the header comments is pretty damming.

It’s probably just laziness / not knowing how to make diffs from 2 different repos.

Re: OpenTofu may be showing us the wrong way to fork

#7
I diffed one of the example files. I don't see clear copying. It looked at a moderate glance to be a different implementation of similar functionality.

I didn't spend time looking at the others as I felt the argument as put forth was already weak.

I'd suggest comparing yourself and not assuming that the author's points are all valid.

Re: OpenTofu may be showing us the wrong way to fork

#9
post #5
post #4

no diff referenced, incompetency or pr campaing from hc

There are links to 3 files in both opentofu and hashicorp. You could get the diff yourself from that. The point about the header comments is pretty damming. It’s probably just laziness / not knowing how to make diffs from 2 different repos.

The bit about the header comments is misleading, as OpenTofu attributes themselves and hashicorp, at least on the first file. If they used any snippets of code from another file in the open source codebase (eg, moved probably has very similar functionality under the hood), then it would be appropriate to attribute that code the the original author.

Re: OpenTofu may be showing us the wrong way to fork

#10
post #6

If true, it's impressively foolish. Still, pre-BUSL Terraform is an achievable goal.

Also an achievable goal is reimplementing the new feature without relying on code which HashiCorp only released under the BUSL. It’s a shame they didn’t do that in this case.
Post reply on HN