From: Sammy Larbi <sam@...>
Date: 2007-04-29T13:00:04+09:00
Subject: Re: DHH vs. WHY style

Peter Cooper wrote:
> On 4/26/07, Ari Brown <ari@aribrown.com> wrote:
>>
>> Don't pick a weird name like Amerthrall (I just made that up). A good
>> bet is always something simple.  For instance, CitiBank doesn't
>> really generate conversations like OOTS generates laughs, but it
>> sticks with people and is easy to remember.
>
>
> Unlike, say, Google? 
I'm not sure that name came from nowhere.... 
(http://en.wikipedia.org/wiki/Googol)  Of course, I assume most probably 
knew that...

> The opposing view doesn't seem to have hurt the
> popularity of Hpricot, Mongrel, Hoe, or, heck, even "Rails" itself, and
> they're some of the biggest Ruby related projects out there ;-)
>
> That said, I must admit I partly agree with you when it comes down to 
> tools,
> rather than brand names. Rails is certainly a brand, and has almost
> certainly been intended to be one from very early on. Same for Hpricot 
> and
> Mongrel, I'd say. Some small library with a niche function though..? 
> I'd say
> your advice would be right for that.

I was never sure if this thread was talking about naming 
classes/packages or a product.  In my view, you should name products 
distinctly, and its quite ok to give them cute names.  But giving 
code-related things names that are nonsensical /is/ nonsensical.  It may 
seem cute, but its often quite useless.

After reading this one, I'm still no closer to knowing if we are talking 
about products or code. =)  But I'm leaning ever closer to knowing I 
just don't know.  =)

Sam