4 ms·

This is a MySQL discussion, but I think it's worth it to say what two things I think keep Postgres from becoming the viable worldwide use-by-default contender t

This is a MySQL discussion, but I think it's worth it to say what two things I think keep Postgres from becoming the viable worldwide use-by-default contender that MySQL became: 1. Branding. First and foremost. MySQL had great documentation, an identifiable logo, and a wonderful name that every non-technical person could remember and identify. Postgresql is just, well, it's a horrible nightmare of a name. People would like to think this doesn't matter but: of course it does. 2. A really slick installer for Windows. You could say this is branding and to some extent it is, but MySQL and its admin tools have a really friendly installer that lets intermediate developers without a lot of DB experience get it up and running with their development environments quickly. I admit it's been a while since I used Postgres's but the fit and polish wasn't there.

ibotty 14y ago
this comment is not only misplaced, it is (at least partly) wrong as well. postgres has great documentation. and had great documentation for quiet a while. see [1]. [1] http://www.postgresql.org/docs/7.3/static/ http://www.postgresql.org/docs/7.3/static/
jeffdavis 14y ago
Let's keep this on topic: in what specific ways has postgresql been more open, and how does that lead to a better developer community and greater value for users? I happen to think the postgres docs are great, and they are open and free unlike the MySQL docs. I have tried following one MySQL doc, only to see it change later and have no way to see the old version. Not a problem for postgres. If you have some suggestions for the docs please submit them to the docs mailing list. Postgres also has 15+ years of history in git, which is extremely helpful. Honestly, I don't know where to start. Postgres is an open community project to the core and benefits from that in so many ways.

ibotty 14y ago

this comment is not only misplaced, it is (at least partly) wrong as well. postgres has great documentation. and had great documentation for quiet a while. see [1]. [1] http://www.postgresql.org/docs/7.3/static/ http://www.postgresql.org/docs/7.3/static/

jeffdavis 14y ago

Let's keep this on topic: in what specific ways has postgresql been more open, and how does that lead to a better developer community and greater value for users? I happen to think the postgres docs are great, and they are open and free unlike the MySQL docs. I have tried following one MySQL doc, only to see it change later and have no way to see the old version. Not a problem for postgres. If you have some suggestions for the docs please submit them to the docs mailing list. Postgres also has 15+ years of history in git, which is extremely helpful. Honestly, I don't know where to start. Postgres is an open community project to the core and benefits from that in so many ways.