On Thu, 13 Jul 2006, Joshua D. Drake wrote:
> Robert Treat wrote:
>> On Thursday 13 July 2006 12:52, Joshua D. Drake wrote:
>>> Well there are a lot of reasons back and forth. The only thing changing
>>> the name to postgres does is simplify the name. Here are the problems
>>> with PostgreSQL:
>>>
>>> Cons for PostgreSQL:
>>> (Yes I am aware of the Trademark, but it is invalid at this point)
>>>
>>> 1. Long domain name
>>
>> It is only 2 more letters... this is a red herring
>
> Oh.. very valid from a communication point of view.
>
> Customer (on phone): What what site should I visit?
> ME: WWW.postgresql.org
> Customer: What?
> Me: www.postgres --- ql.org
> Customer: Why the ql?
>
> And yes this does happen. The name by nature of how it is spelled is
> difficult to say without confusing someone. Thus the domain name being longer
> is relevant.
Just as an aside ... http://www.postgres.org will work, and gets them to
the proper site too ... where we've been able to, we've made sure that
both could be used ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
