telekinesis VS opentofu

https://payperrun.com/%3E/search?displayParams={%22q%22:%22S...

(There are quite a few, you might want to filter by date!)

Hey everyone, I just made this thread easier to search through here:

https://payperrun.com/%3E/search?displayParams={%22q%22:%22D...

It uses LLM embeddings to sort postsby semantic proximity, but you can also filter out posts with comma separated values like this:

https://news.ycombinator.com/item?id=33118584

[Shameless plug: I found all these on my llm-embedding based search engine I launched today: https://payperrun.com/%3E/search?displayParams={%22q%22:%22A...

It's much better than HN's default search: https://hn.algolia.com/?q=Ask+HN%3A+What+do+you+regret+doing... ]

https://payperrun.com/%3E/search?displayParams={%22q%22:%22A...

There have been a few attempts at a crowdsourced-rank search engine (which is similar to what you're suggesting - people indexing the content), but it seems to be a hard cookie, most of the examples of similar ideas I could find on ProductHunt or ShowHN seem dead:

https://payperrun.com/%3E/search?displayParams={%22q%22:%22c...

(btw, I just launched this llm-embedding based search service that lets you check if a startup idea has already been tried/failed).

I don't know if this idea has a higher death rate than the baseline, but my guess is Google/PageRank is good enough for most use-cases, and then if you want quality sources, you can just follow them on YouTube, Twitter, Instagram, etc. Wait, maybe I shouldn't try to compete with Google?

I like the section on how it works: https://payperrun.com/%3E/search?display=How%20this%20servic...

The vector search is using https://lancedb.com/ and OpenAI embeddings.

Behaves as I expected now!

I went here looking for more info about payperrun https://payperrun.com/%3E/welcome and clicked on the "Spotlight" section and saw 4 popups blocked - I never see popups anywhere these days and have to admit that sends me away pretty quickly.

Hey!

> With OpenTofu exclusive features making such an early debut, is the intention to remain a superset of upstream Terraform functionality and spec, or allow OpenTofu to diverge and move in its own direction?

The intention is to let it diverge. There will surely be some amount of shared new features, but we're generally going our own way.

> Will you aim to stick to compatibility with Terraform providers/modules?

Yes.

Regarding providers, we might introduce some kind of superset protocol for providers at some point, for tofu-exclusive functionality, but we'll make sure to design it in a way where providers keep working with both Terraform and OpenTofu.

Regarding modules, this one will be more tricky, as there might Terraform languages features that aren't supported in OpenTofu and vice-versa. We have a proposal[0] to tackle this, and enable module authors to easily create modules with support for both, even when using some exclusive features of any one of them.

> Is the potential impact of community fragmentation on your mind as many commercial users who don’t care about open source ideology stick to the tried-and-true Hashicorp Terraform?

We've talked to a lot of people, and we've met many who see the license changes as a risk for them, while OpenTofu, with its open-source nature, is the less-risky choice. That includes large enterprises.

> Is there any intention to try and supplement the tooling around the core product to provide an answer to features like Terraform Cloud dashboard, sentinel policies and other things companies may want out of the product outside of the command line tool itself?

That's mostly covered by the companies sponsoring OpenTofu's development: Spacelift (I work here), env0, Scalr, Harness, Gruntworks.

[0]: https://github.com/opentofu/opentofu/issues/1328

Please remember to file in a calm and orderly fashion toward the exits and remember: IBM killed Centos for profit.

Terraform users can pick up their new alternative here:

https://opentofu.org/

and for those of you with Vault, you can find your new alternative here:

https://openbao.org/

OpenTofu v1.6

Note: New versions of Terraform will be placed under the BUSL license, but everything created before version 1.5.x stays open-source. OpenTofu is an open-source version of Terraform that will expand on Terraform's existing concepts and offerings. It is a viable alternative to HashiCorp's Terraform, being forked from Terraform version 1.5.6. OpenTofu retained all the features and functionalities that had made Terraform popular among developers while also introducing improvements and enhancements. OpenTofu is not going to have its own providers and modules, but it is going to use its own registry for them.

opentofu is solving this with proper state encryption support: https://github.com/opentofu/opentofu/issues/874

As with all other Linux Foundation and CNCF projects, OpenTofu is guided by the Technical Steering Committee(TSC), which works in open collaboration with the community on the development of new features, upgrades, bug fixes, etc. The current TSC consists of representatives from Harness, Spacelift, Scalr, Gruntworks, and env0.

Note: New versions of Terraform will be placed under the BUSL license, but everything created before version 1.5.x stays open-source. OpenTofu is an open-source version of Terraform that will expand on Terraform's existing concepts and offerings. It is a viable alternative to HashiCorp's Terraform, being forked from Terraform version 1.5.6. OpenTofu retained all the features and functionalities that had made Terraform popular among developers while also introducing improvements and enhancements. OpenTofu works with your existing Terraform state file, so you won't have any issues when you are migrating to it.