I think the author makes a hard distinction between consumer products and infrastructure/engineering products. The Shelby Cobra has a funny name, but its engine is the memorably named V8. The Hoover Dam is a dam, and the Golden Gate Bridge is a bridge.
We can argue about namespace pollution and overly long names, but I think there's a point there. When I look at other profession's jargon, I never have the impression they are catching Pokemon like programmers do.
Except for the ones with Latin and Greek names, but old mistakes die hard and they're not bragging about their intelligibility.
>I think the author makes a hard distinction between consumer products and infrastructure/engineering products.
Which is really funny considering he talks about emacs.
> The Hoover Dam is a dam, and the Golden Gate Bridge is a bridge.
Nothing stops the author from using "Libsodium crypto lib" and "Zephyr RTOS".
> but its engine is the memorably named V8.
You're misremembering. It's the "Windsor V8." Or more specifically the "4.8L Windsor Ford V8."
Also the author misses how elements, species and astronomical objects are named. After random places, people, games, fictional characters, etc.
Names are just names. It’s nice if they are kind of unique and have no collisions.