Why does default max_connections differ in the default parameter groups for RDS MySQL and RDS MariaDB?

I'd like to understand why the default max_connections value differs between MySQL and MariaDB, and what that means for memory requirements of the different databases.

I tested this using the most recent versions available, MySQL Community 8.0.27 and MariaDB 10.5.12. By default, MySQL 8.0.27 will use the default.mysql8.0 parameter group, and MariaDB 10.5.12 uses default.mariadb10.5.

Those parameter groups use these calculations for setting the max_connections variable:

default.mysql8.0 : {DBInstanceClassMemory/12582880} default.mariadb10.5 : LEAST({DBInstanceClassMemory/25165760), 12000)

I tested them with db.t3.micro instances (1 GB RAM), and the observed max_connections values are in line with those formulas:

MySQL [(none)]>  SHOW VARIABLES LIKE 'max_connections';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| max_connections | 63    |
+-----------------+-------+
 

MariaDB [(none)]>  SHOW VARIABLES LIKE 'max_connections';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| max_connections | 31    |
+-----------------+-------+

Why does AWS choose to set max_connections differently between MySQL and MariaDB? I understand that the MariaDB and MySQL projects have diverged, but this seems like a pretty big difference. And related to this, is this an indication that MariaDB requires more memory than MySQL for similarly sized workloads?