Was an Emacs package before that.

TIL; thanks.

Pretty sure EMACS beat Kubernetes to the punch. This Helm, too, is pretty old now.

Complaining about names is ridiculous. There are only so many names to go around, and there's almost no overlap in use-case or userbase between a synthesizer and a throwaway piece of business software for Yet Another Soulless Cloud Ecosystem.

Naming things isn't hard. What's hard is that people feel possessive over English words. You probably share your name with hundreds of thousands of people in your country.

Comparing names of products to names of people simply doesn't make sense. Ideally you want to pick a name for your product which stands out and people will remember. You shouldn't need to clarify by saying 'use Kubernetes Helm' or 'use the synthesiser Helm'.

However people aren't usually named this way, and so you cannot compare names this way.

First release of Kube Helm: Feb 2016

Earliest commit in the synth Helm repo: 2013

Earliest commit in the Emacs Helm repo: <=2007

First time someone called a ship helm a helm: ???

First time a Viking called a helmet a helm: ???

So, who cares really

You're extrapolating a bit too far here; it somewhat detracts from the point you're trying to make.

Yeah they really should have checked out the Helm synth before they named the Kubernetes thing!

Good point; I assumed that it was being posted here because it was a new project. My point still stands though, but in the opposite direction.

If I was looking for a virtual synth deck and came to you asking for a recommendation and you said Helm but actually meant the Kubernetes Helm not the synth Helm, you would have a very solid point. But you would also be an idiot.

Hint, hint.

Quite, because who would actually do that?

Do you know that "Helm" is a German word for "helmet"? That's what happens when you name a project after a dictionary word.

I did not; TIL!

But you could not tell which helm was being referred to on the HN news link title, a (Synth) or (Kubernetes) would do. OP has a good point.

To be fair, it's been pointed out to me that quite a few projects which I wasn't aware of are named Helm. But this does further reinforce my point.

If you came into the comments section to discuss Kubernetes Helm before opening the link and understanding what it was referring to, then that's on you not the project.

And all these audiophiles didn't know about this completely different app in an area they probably don't even know exists? Serenity now!

Of course this is _very_ difficult for me, a DevOps engineer who deploys VSTs via Kubernetes, but I think I'll survive

Well if you can't cope then you should probably be looking for a new job ;)