Thread: Another reason to hate our name...
http://www.google.com/trends?q=postgresql%2Cpostgres% 2Cdb2&ctab=0&geo=all&date=all (Yes, I tried with MSSQL, Oracle and MySQL as well... the results... weren't pretty) -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Jim, > (Yes, I tried with MSSQL, Oracle and MySQL as well... the results... > weren't pretty) There are so many problems with that tool from a data perspetive that I resolved to ignore it from the day I saw it. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
Hello Jim, On Wed, 2006-08-09 at 18:21 -0500, Jim Nasby wrote: > http://www.google.com/trends?q=postgresql%2Cpostgres% > 2Cdb2&ctab=0&geo=all&date=all > > (Yes, I tried with MSSQL, Oracle and MySQL as well... the results... > weren't pretty) Did you also try with MS, OracleSQL and My? Removing SQL from Postgre(s) is the same as this, I think. I don't see a point in changing our name -- let's focus on new features, new marketing ideas, etc. If a person does not use PostgreSQL because of our name, then he/she may surely drop, I don't care. Cheers, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
Attachment
Hi,
I share Devrim's view. As someone who is principally concerned with the business perception of PostgreSQL, as opposed to its technical noteworthiness, I can't see a lot of point in attempting a rebranding exercise at this point in time. Energies would be better directed at marketing the product more aggressively, I feel.
The PostgreSQL 'brand', for all its awkwardness, is well established and phenomenally successful (though there is infinitely more that can be achieved). Its name is just not a strong aspect of its 'sales appeal'. There are plenty of precedents for this with commercially successful products, in my subjective opinion.
I would rather see the debate move to just that, how to better present PostgreSQL's commercial attractiveness - cost benefits, return on investment, strategic advantages etc...
Regards,
Liam
_____________________________________________
Liam O'Duibhir - Product Manager - Open Source Software
Fujitsu Australia Software Technology
14 Rodborough Road, Frenchs Forest NSW 2086
Tel: (61-2) 9452 9068 Fax: (61-2) 9975 3779
Mob: 0423 025 852 Email: LiamOD@fast.fujitsu.com.au
http://fastware.com.au/postgresql.html> -----Original Message-----
> From: pgsql-advocacy-owner@postgresql.org [
mailto:pgsql-advocacy -> owner@postgresql.org] On Behalf Of Devrim GUNDUZ
> Sent: Thursday, August 10, 2006 10:34 AM
> To: Jim Nasby
> Cc: PostgreSQL Advocacy
> Subject: Re: [pgsql-advocacy] Another reason to hate our name...
>
> Hello Jim,
>
> On Wed, 2006-08-09 at 18:21 -0500, Jim Nasby wrote:
> >
http://www.google.com/trends?q=postgresql%2Cpostgres%> > 2Cdb2&ctab=0&geo=all&date=all
> >
> > (Yes, I tried with MSSQL, Oracle and MySQL as well... the results...
> > weren't pretty)
>
> Did you also try with MS, OracleSQL and My? Removing SQL from
> Postgre(s) is the same as this, I think.
>
> I don't see a point in changing our name -- let's focus on new
> features, new marketing ideas, etc. If a person does not use
> PostgreSQL because of our name, then he/she may surely drop, I don't
> care.
>
> Cheers,
> --
> The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
> Managed Services, Shared and Dedicated Hosting
> Co-Authors: plPHP, plPerlNG -
http://www.commandprompt.com/
"PostgreSQL. It's easier to use than to pronounce." -- Bruce Alderman "It Seems to Me..." http://www.brucealderman.info/blog/ A candle loses nothing by lighting another candle. > -------- Original Message -------- > Subject: Re: [pgsql-advocacy] Another reason to hate our name... > From: "Liam O'Duibhir" <liamod@fast.fujitsu.com.au> > Date: Thu, August 10, 2006 12:44 am > To: devrim@commandprompt.com > Cc: pgsql-advocacy@postgresql.org > > > > Hi, > > I share Devrim's view. As someone who is principally concerned with the business perception of PostgreSQL, as opposed toits technical noteworthiness, I can't see a lot of point in attempting a rebranding exercise at this point in time. Energieswould be better directed at marketing the product more aggressively, I feel. > > The PostgreSQL 'brand', for all its awkwardness, is well established and phenomenally successful (though there is infinitelymore that can be achieved). Its name is just not a strong aspect of its 'sales appeal'. There are plenty of precedentsfor this with commercially successful products, in my subjective opinion. > > I would rather see the debate move to just that, how to better present PostgreSQL's commercial attractiveness - cost benefits,return on investment, strategic advantages etc... > > Regards, > > Liam > > _____________________________________________ > > Liam O'Duibhir - Product Manager - Open Source Software > > Fujitsu Australia Software Technology > > 14 Rodborough Road, Frenchs Forest NSW 2086 > > Tel: (61-2) 9452 9068 Fax: (61-2) 9975 3779 > > Mob: 0423 025 852 Email: LiamOD@fast.fujitsu.com.au > > http://fastware.com.au/postgresql.html >
On Thu, Aug 10, 2006 at 03:33:31AM +0300, Devrim GUNDUZ wrote: > Hello Jim, > > On Wed, 2006-08-09 at 18:21 -0500, Jim Nasby wrote: > > http://www.google.com/trends?q=postgresql%2Cpostgres% > > 2Cdb2&ctab=0&geo=all&date=all > > > > (Yes, I tried with MSSQL, Oracle and MySQL as well... the results... > > weren't pretty) > > Did you also try with MS, OracleSQL and My? Removing SQL from Postgre(s) > is the same as this, I think. How is 'My' at all equivalent to 'MySQL'?? Apparently my point was too subtle... If people weren't inconsistently searching for Postgres instead of PostgreSQL we would be above DB2 in search volume, which I think is a milestone. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461