| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "J(dot) Andrew Rogers" <jrogers(at)neopolitan(dot)com> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] What can we learn from MySQL? |
| Date: | 2004-04-23 19:07:08 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB34101ADD5@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
J. Andrew Rogers wrote:
> No. The greatest strength of Postgres, marketing-wise, are technical
> and is what drives its growth today. I think most of the ease-of-use
> issues are in the packaging of the larger Postgres product and
mid-level
> developer documentation, both of which seem to be eminently solvable
> problems. I think improved default product packaging would remove 80%
plus, up to this point AFAIK the postgresql docs have not been quoted
here:
which speaks volumes ;)
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-04-23 19:13:15 | Re: [pgsql-advocacy] What can we learn from MySQL? |
| Previous Message | Robert Treat | 2004-04-23 19:04:53 | Re: [pgsql-advocacy] What can we learn from MySQL? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-04-23 19:13:15 | Re: [pgsql-advocacy] What can we learn from MySQL? |
| Previous Message | Robert Treat | 2004-04-23 19:04:53 | Re: [pgsql-advocacy] What can we learn from MySQL? |