4 ms·

MySQL has a incomparable better marketing and internet presence (well written documentation and community sites). Its success was due to illusion of simplicity

by c00p3r 16y ago

MySQL has a incomparable better marketing and internet presence (well written documentation and community sites). Its success was due to illusion of simplicity and easiness + massive community of believers ^_^ PostreSQL sites is rather shy comparing to them.

omarqureshi 16y ago
Have you seriously compared MySQLs documentation to Postgres? It has such mindblowingly retarded gems such as http://dev.mysql.com/doc/refman/5.1/en/connection-access.html http://dev.mysql.com/doc/refman/5.1/en/connection-access.htm.... I mean people actually sat around and thought this was the best way to do user auth.
- c00p3r 16y ago
  Feeling is what matters, especially for newbies.. Documentation should be written is a light, non-boring style. Django's or Android's is a best examples.
  - moe 16y ago
    Django's or Android's is a best examples Yes, but how can you put those in the same bucket with MySQL's? http://dev.mysql.com/doc/refman/5.5/en/mysqldump.html http://dev.mysql.com/doc/refman/5.5/en/mysqldump.html vs http://www.postgresql.org/docs/current/static/app-pgdump.html http://www.postgresql.org/docs/current/static/app-pgdump.htm... Note how half the page of the mysqldump docs is spent explaining the braindead semantics and dangerous interaction between --opt* and pretty much everything else. Moreover the MySQL docs generally read as if they were written by a monkey with ADD: mysqldump can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the --quick option (or --opt, which enables --quick). The --opt option (and hence --quick) is enabled by default, so to enable memory buffering, use --skip-quick. This is frankly just a random example from recent memory. Compare any two pages and you get similar results.

by c00p3r 16y ago

omarqureshi 16y ago

Have you seriously compared MySQLs documentation to Postgres? It has such mindblowingly retarded gems such as http://dev.mysql.com/doc/refman/5.1/en/connection-access.html http://dev.mysql.com/doc/refman/5.1/en/connection-access.htm.... I mean people actually sat around and thought this was the best way to do user auth.

c00p3r 16y ago
Feeling is what matters, especially for newbies.. Documentation should be written is a light, non-boring style. Django's or Android's is a best examples.
- moe 16y ago
  Django's or Android's is a best examples Yes, but how can you put those in the same bucket with MySQL's? http://dev.mysql.com/doc/refman/5.5/en/mysqldump.html http://dev.mysql.com/doc/refman/5.5/en/mysqldump.html vs http://www.postgresql.org/docs/current/static/app-pgdump.html http://www.postgresql.org/docs/current/static/app-pgdump.htm... Note how half the page of the mysqldump docs is spent explaining the braindead semantics and dangerous interaction between --opt* and pretty much everything else. Moreover the MySQL docs generally read as if they were written by a monkey with ADD: mysqldump can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the --quick option (or --opt, which enables --quick). The --opt option (and hence --quick) is enabled by default, so to enable memory buffering, use --skip-quick. This is frankly just a random example from recent memory. Compare any two pages and you get similar results.