I think it also comes down to the fact that many hosting providers (including cloud providers like AWS) offer up MySQL-imaged machines, with back-up and other processes around that.
So, on the dev front, I'm going to be inclined to stick with MySQL on my local dev machine, knowing that I'm also deploying to MySQL in production. Even if MariaDB is designed as a drop-in replacement, there can be differences between the two that impact how code runs. This is especially true when one (MariaDB) is updated more frequently.
I'm sure I can roll my own MariaDB server on an EC2 machine vs going with RDS, then also migrate my dev machine to MariaDB as well. But, I've just not seen a compelling reason to undertake that effort as of yet.
Comments
I think it also comes down to the fact that many hosting providers (including cloud providers like AWS) offer up MySQL-imaged machines, with back-up and other processes around that.
So, on the dev front, I'm going to be inclined to stick with MySQL on my local dev machine, knowing that I'm also deploying to MySQL in production. Even if MariaDB is designed as a drop-in replacement, there can be differences between the two that impact how code runs. This is especially true when one (MariaDB) is updated more frequently.
I'm sure I can roll my own MariaDB server on an EC2 machine vs going with RDS, then also migrate my dev machine to MariaDB as well. But, I've just not seen a compelling reason to undertake that effort as of yet.