On Fri, 12 Mar 2021, Sven Panne wrote:
Even if it's called "gnlpft" and it is the 1st hit on Google
I think the correct name must be "gnlpfth", because 'h' stands for the Heart that beats for you night and day.
Another good example: "aeson". It's not really the first name coming to your mind when you think about JSON, but people don't have a problem discovering it.
This was the first example I also had to think of.
A more problematic thing than the package names IMHO is the choice of names for the hierarchical modules within a package: If things somehow clash by accident here, you have bigger problems. There is no process whatsoever (at least I don't know one) how these names are allocated. There were some proposals by Malcolm W. and Simon M. some 10-20 years ago IIRC, but these were only rough sketches.
Most module names today end up in the "Data" folder. :-)