> There are rumblings that the MySQL project is rudderless after Oracle fired the team working on the open-source project in September 2025.

Not just the open-source project; 80%+ (depending a bit on when you start counting) of the MySQL team as a whole was let go, and the SVP in charge of MySQL was, eh, “moving to another part of the org to spend more time with his family”. There was never really a separate “MySQL Community Edition team” that you could fire, although of course there were teams that worked mostly or entirely on projects that were not open-sourced.

▲

menaerus 2 days ago | parent [-]

Wouldn't Oracle need those 80%+ devs if they wanted to shift their efforts into Heatwave? That percentage sounds too huge to me and if true I believe they won't be making any larger investments into Heatwave neither. There's several core teams in MySQL and if you let those people go ... I don't know, I am not sure what to make out of it but that Oracle is completely moving away from MySQL as a strategic component of their business.

▲

Sesse__ a day ago | parent [-]

> Wouldn't Oracle need those 80%+ devs if they wanted to shift their efforts into Heatwave?

They would, so Heatwave is also going to suffer over this.

	▲	menaerus 14 hours ago \| parent [-]
		So, AI ate the cake ... I always thought that the investment that Oracle needs to make for MySQL is peanuts compared to the Oracle's total revenue and the revenue MySQL is generating. Perhaps the latter is not so true anymore.