A new write and space optimized storage engine for MySQL is here

This is really not better. Well… not much better.

I've spent my entire life reading, writing, condensing and explaining stuff, and I'm pretty good at it, but I find reading this stuff intensely tiring.

But my underlying concern remains. Why are people who want to communicate important ideas leaving it to Claude — which writes like an obscurantist gnome wizard from a bad fantasy novel — to do so, only to lead us to use LLMs to corral it into a less gnomic form?

People used to describe their own products in their own words.

Not sure at the moment what they are moving to or have moved to. I just heard from Mark Callaghan few months ago about the archiving, not much besides that.

My understanding is that Meta continues to use MySQL and specifically MySQL, but have decided they aren't investing in upgrading to the newer MySQL versions. And possibly their fork contains a lot of custom patches beyond just MyRocks. So as a consequence of this decision they no longer support MyRocks for newer versions of MySQL and otoh MySQL no longer supports the 5.x versions.

Of course MySQL has obviously the deep support for custom storage engines, then it has loadable functions, auth, component service and these are currently internal extensibility but going forward we are working on a way to manage this extensibility externally through a new proposal which I will be going over in the upcoming MySQL contributor summit in November. Postgres though highly externally extensible doesn't cut into the core like MySQL or MariaDB does thus making it hard to for example make TidesDB integration as TidesDB has to handle the MVCC, for example. OrioleDB is another example and it has to utilize a custom Postgres fork for this reason, the core not being very extensible, though I hear this is being worked on heavily.