Subject: Re: [isocpp-lib-ext] std::colony name brainstorming
From: Jeff Garland (jeff_at_[hidden])
Date: 2021-02-10 06:55:41
> On Feb 9, 2021, at 11:03 PM, Ville Voutilainen via Lib-Ext <lib-ext_at_[hidden]> wrote:
> Well, old houses are demolished, new ones are built. I fail to see how
> houses and neighborhoods aren't dynamic.
I owned the same house for ~25 years in an unchanging neighborhood. The cathedral in Prague was how old again? Sure, thereâs change, but it's utterly the wrong time scale of change for an analogy to a container that is designed to handle âbullet objects in a game that last 1 secondâ or data in high frequency trading. Colony invokes âslow movingâ for me â not fast.
>> So letâs do some other analysis. If we put âcolonyâ into google, weâre not going to find plf::colony at all â in fact weâre not going to find any results related to computer science in any way. Put in âcolony computingâ or âcolony data structure' â interestingly, and I think unfortunately for this name, âant colony optimizationâ comes up (new to me today). This data structure is unrelated to these optimization algorithms â since they are graph traversal algorithms. My conclusion is that the name is completely novel, possibly misleading, and not obvious to the target audience (computer scientists).
> When I google for "colony c++", plf::colony is the first hit. What do
> you mean by suggesting that the target audience
> here is computer scientists?
And the search âcolony data structureâ brings up âant colonyâ algorithms - not related, confusing. plf::colony is super specific and wonât be remembered. Why would âcomputer scientists' go looking for history on âcolony data structureâ. Because many developers have a background in computer science and they know data structures are often backed by mathematics.
> I have a very different target audience
> for colony - programmers.
See above, a large set of programmers have degrees in computer science. Even self taught programmers will find a wealth of information on stack, queue, list and other basic data structures. Colony has no precedent in literature beyond Mattâs writing.
> When toying
> with the idea of changing the name, we need to consider whether the
> suggested alternative name is as
> good as colony is after being given the room/house explanation, not
> before that explanation is given, as far
> as I care.
Agree. In general, I have a low opinion of analogy based names because they break down too easily. Youâre the only one that addressed the âmeritsâ or non-merits of my suggestions which Iâll come back to in another mail.
> On Feb 10, 2021, at 1:43 AM, Ville Voutilainen via Lib-Ext <lib-ext_at_[hidden]> wrote:
> On Wed, 10 Feb 2021 at 10:21, Richard Hodges via Lib-Ext
> <lib-ext_at_[hidden]> wrote:
>> Colony is a bad name for this container on its own merits
> ..and those merits on which it's a bad name are..?
> This is what makes these discussions a waste of time. Claims without
> rationale, that is.
Please reread my mail. 1) no precedence in computer science literature (novel), 2) a class of algorithms that have âcolonyâ in the name (confusing), and 3) based on a bad analogy (at least for me and several others). Thatâs rationale. The followup was really +1 to point #3.
It might be a waste of time for other reasons, but not that one.
> And also name suggestions without rationale, of course. And complaints
> that the name
> is bad without suggestions for alternatives that don't immediately stink.
All my suggestions were at least motivated with some logic. Based on the actual properties of the container that matter to users. The logic is there to be discussed. Some others may have suggested better â tbd.
SG14 list run by firstname.lastname@example.org
Older Archives on Google Groups