3 ms·

I remember years ago when every new PHP application would have "PHP" before its name. PHPNuke, PHPMyadmin, etc, etc. Seeing the same trend with Go now. Why add

• sanderjd 10y ago
  Another real question: What is the better approach? Generic names (eg. "bgpd")? That seems decent if you have an over-arching project to group the generic stuff under (eg. "Apache httpd"). Making up codenames for everything (eg. "Zebra")? It's a pain to think of those, and they're rarely descriptive or meaningful. I don't really like the language-name-prefix thing either. It makes the language seem like the important thing about the project. Sometimes it is the most important thing, but even then, that is mostly only true at the beginning of a project when attracting contributors is most critical. But I'm not sure the other approaches are much better.