Re: name Re: Dropping postgres as a whole.

From: Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: PostgreSQL Advocacy List <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: name Re: Dropping postgres as a whole.
Date: 2007-09-27 18:42:53
Message-ID: 20070927184253.GA8229@yellowbank.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

2007-09-27_14:24:47-0400 "Joshua D. Drake" <jd(at)commandprompt(dot)com>:

> The reason I brought up Pg as a whole is:
>
> 1. It is short and sweet

I think that's a problem. I think Pg might be good name for a variable
in some code, but not in written documentation. My primary concern is
the search engines. Google is going to be the first place many, many
people go to look for information. Both 'PostgreSQL' and 'Postgres'
unambiguously refer to a specific thing. For better or worse, search
engines have a huge impact on product visibility, and even usability.
Try searching for information on 'screen' for example.

I do think it's fair to compare the merits of choosing a name based on
its written impact vs. how it's spoken though.

I wonder what the record is for the longest running listserv thread.

--
Ron Peterson
https://www.yellowbank.com/

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2007-09-27 18:50:52 Re: Using Postgres as an alias
Previous Message Robert Treat 2007-09-27 18:41:52 Re: Using Postgres as an alias