As an application developer, I remember wrestling with some really annoying stuff on the application side to deal with MySQL. IIRC, it was something like the de

As an application developer, I remember wrestling with some really annoying stuff on the application side to deal with MySQL. IIRC, it was something like the default ORM for a python-based framework requiring a reflection API that Postgres and SQLite have and MySQL doesn't. This and other war stories probably generalizes to many other application developers preferring Postgres, but there's a ton of people using MySQL, so that probably means that it solves a bunch of the problems that the wizards in operations have. That's why I listed both. I'd use and recommend Postgres as a default in a heartbeat based off personal experience, but I wouldn't have personal experience with MySQL's strengths and people use and recommend it as well.