You know, it bothers me so much when this shows up as a criticism. You didn’t say it as one, but when I released the Q platform, for social networking apps, which we worked for years on since 2010 and earlier, people told us “rename your library, there is already a famous library Q for promises”.
Well, now promises are native and that Q library isn’t a big deal.
But meanwhile I had to constantly defend with logical arguments, until I gave up and had our team overhaul the entire codebase and marketing JUST so the very vocal squeaky wheel developers could get past the naming issue and focus on what the actual benefits of the platform are.
I've never heard of your "platform." I've heard of the Q promises library.
At some point isn't it just easier to recognize that choosing a name requires some basic amount of due diligence? I've helped choose names for multiple products, in every case we had to put some thought and research into it.
> But meanwhile I had to constantly defend with logical arguments
There's no "logical argument" in this case. You're confusing rhetoric with logic.
But, at the same time, sometimes when dev-teams build a system/product named after a single short common word (Looking at you, go!), or a single letter, it gets to be hard to search for and find relevant results. (The "go-lang" convention didn't get widely adopted/used until go had been out there for a while).
Well, now promises are native and that Q library isn’t a big deal.
But meanwhile I had to constantly defend with logical arguments, until I gave up and had our team overhaul the entire codebase and marketing JUST so the very vocal squeaky wheel developers could get past the naming issue and focus on what the actual benefits of the platform are.
Found one of the threads: https://news.ycombinator.com/item?id=7334367