MySQL's decline under Oracle's stewardship is evident, prompting calls for users to switch to MariaDB. Git commits for MySQL have sharply decreased, raising concerns about its future as an open source project. Oracle's acquisition of Sun Microsystems in 2009 was initially met with skepticism, and over the years, the community around MySQL has eroded. Contributions from developers are often ignored, with many feeling that their inputs are not genuinely valued. In contrast, MariaDB maintains an active and transparent development process, allowing anyone to submit code and engage with the community. Technically, MySQL has faced significant issues since 2022. The release of MySQL 8.0.29 introduced critical bugs that led to data corruption, with fixes lagging behind user needs. Major releases have been sparse, with MySQL 8.1 only a preview in 2023 and the 8.4 LTS version in 2024 disappointing users with its lack of new features. Performance benchmarks show a decline, particularly in write-heavy workloads, and many users struggle with upgrades due to deprecated features. With Oracle reducing its MySQL workforce and releasing fewer bug fixes, the platform's viability is in question. The security implications of MySQL’s closed development model raise alarms. In 2025, MySQL reported 123 security vulnerabilities (CVEs) while MariaDB only had 8. Many MySQL CVEs lack detailed information, leaving users reliant on Oracle's assurances about fixes. This opacity contrasts sharply with the open discussions and transparency seen in other open source projects. Users increasingly feel pressured to migrate to Oracle's closed services, like Heatwave, which further limits their control over their data. Overall, the message is clear: sticking with MySQL poses substantial risks, and alternatives like MariaDB are readily available, offering a more trustworthy path forward.