Earlier quoted context omitted.
I think the discussion point was php was too easy and that encouraged new developers or less hardcore developers to adopt it. Some of the defaults like globals being turned on by default led to security holes. How people were creating sql statements at the time concating strings led to sql injection issues. There were never any bad parts . There are new features like the spread operator that are newer and not availab…
> Postgres needs to run under a specific os user. That alone makes it a poor MySQL replacement Where did you get that idea? Postgres can run as any user. In fact, I recently switched my applications to use Postgres even during unit tests (instead of SQLite), i.e. that testing instance runs under my normal login user. That change actually made the CI go faster because compiling the Go SQLite driver takes much much lon…
MySQL 5.7+ is decent. Where it loses out to PostgreSQL is the lack of plugins/extensions. PostgreSQL is extensible in ways MySQL users can only dream of (e.g. timescaledb, pg_trgm)
Also, the forking of MySQL and MariaDB has resulted in 2 very similar databases that people consider interchangeable - but aren't. There's plenty of "gotchas" if SQL is meant to run on both.