throwawayllaq

Modern search engines and LLMs have no trouble distinguishing between different things with the same name. Google Trends will even show you something is a product, a service, a book, whatever. If you ask a LLM "what is this tofu infrastructure as code tool I keep hearing about?" it will 100% tell you about the tool and not the food.

It's more practical and less hilarious.

There is a thing called acronym, abbreviation, or initialism copyright.

For Hashicorp's Terraform, "TF" is a well recognized abbreviation.

Hashicorp can't prohibit anyone from using "TF" in all areas, but it can argue that "OpenTF" confuses users that expect anything "TF" to mean "Terraform".

You can probably create a "OpenTF juice maker" without problem but OpenTofu especifically is in the same area as Hashicorp's Terraform, so it's better to avoid any trouble there.

This discussion ship has sailed.

I think OpenTofu should embrace the negative connotations. Go crazy, make everything Tofu, that's the goal. It'd be a nice side history for marketing purposes. I doubt anyone would not use the tool because of it and others would get a good chuckle.

I just read the plot and now I understand the reference.

So it was a clever comment but not particularly a joke (maybe a not so good one?)

I can imagine a piece of tofu with robotic arms terraforming stuff. Pretty easy.

Or a globe with a tofu on top. Make the tofu evil/insane and create a story it wants to transform every plant in tofu.

Wny OpenTransform?

I took it as it was written, word by word.

To be fair, I'm not saying it should hold all the knowledge in the world. I just expect it to give me short answers to pretty simple questions.

For example: "Hey Google, what are the biggest cities in Australia?" could be answer by "Hey Dave, the biggest cities in Australia are Sydney, Melbourne, and Brisbane" OR "I don't know this information and can't search the web for it"... but it just answers "I did not understand" over and over for anything.

It seems to only understand (sometimes): "play X on spotify", "directions to X", "restaurants" ... anything in slightly more complex natural language is a no go.

I expected TTS/STT to be a solved problem now with decades of work on it.

I can understand LLMs having greater latency but all flagship smartphones have inference accelerators these days.

A good response is just an API away, which Google Assistant already does I think (it doesn't give me an instantaneous answer ever).

The original way of making money with FOSS that folks like Hashicorp and InfluxData fail to understand while they push for unicorn status.

This is MariaDB, a MySQL fork.

My exact issue today too. To my surprise, I was talking in Portuguese and it was answering in Portuguese even though my phone is set to English. Then I opened Spotify and it started to talk in English and misunderstand everything.