Funnily enough, I have not been using MySQL for the last 10 years either, because I switched to Postgres and never went back.

Fair, but why comment on MySQL's supposed deficiencies if your knowledge of it is so out-of-date?

But vanilla PG didn't get good master / slave feature until "recently" so you were running without replicas in the last 10 years?

https://www.postgresql.org/about/news/1235/

Your link is from 9 years ago.

The release from 9 years ago was not even close to what MySQL was offering at the time.

This happens when someone asks a versus question on a Sunday.

Unfortunately this is not true, I found it used in the most unexpected places, even new developments as old as 2-3 years.

That's mostly because it's the default in some versions and the developers don't know/care that MyISAM is dangerous (as it's not transactional and it will transparently ignore any kind of foreign key statement).

We specifically had to switch to MyISAM for some things when upgrading from 5.5 to 5.7, in 2017. We were hitting InnoDB’s 4k row limit in many cases (without clobs). Fortunately the tables in question are filled once, updated a couples times right after, and from then on only read, so lack of ACID is ok just for that. (All the real transactional tables are InnoDB.)