Now that there is testing like https://turso.tech/blog/introducing-limbo-a-complete-rewrite... going on, tbh the testing described in the linked piece doesn't seem so good.
https://github.com/rqlite/rqlite/blob/master/CHANGELOG.md#10...
Applying it to software is a logical step if you want similar levels of quality assurance.
Do you need that level of assurance for a database? Probably not in most cases. But I think it's a reasonable thing to mention on a post that is touting database reliability, especially because there are real databases that do use it.
Or if you really wanna keep the SQLite theme: https://github.com/losfair/mvsqlite
Why promote the vaporware project when comparing with something that's been in development for 10 years?
The cargo culting bit is using vaporware that was just in the news cycle to shout down good work that has been done for decades.
Probably because it's been in the news very recently and most people learned of DST in software from it.