What‘s the point of it, by the way? Why would one start a new project based on MySQL instead of postgres today?
1. easier to configure and manage
2. faster for read-heavy workloads
3. has pluggable storage engine (though, if you care about this, then 1. likely doesn't matter anymore)
MySQL has had multiple viable storage engines for most of its existence. MyISAM, InnoDB and more recently MyRocks.
https://www.postgresql.org/docs/current/ddl-foreign-data.htm...
https://dbaclass.com/article/how-to-access-csv-files-on-file...
What you say looks powerful but Facebook added their MyRocks to MySQL.
Besides that, there are still some points where the MySQL and/or the tooling around it simply performs better than Postgres. Anything to do with replication and big table migrations comes to mind.
RocksDB is a single node very efficient (better than Cassandra's in the 2.x/3.x releases, not sure about now) single node LSM implementation.
Features, better ACID (at least historically) and maybe better standards compliance.
The big one for me is being able to run schema changes in transactions, which makes it easy to roll back a failed migration.
Not being Oracle is a huge advantage ;)
Otherwise, why not? It’s basically a Chevy vs Ford decision.
1) companies that sell non oss commercial licenses for their AGPLed software that they own the copyright to and want you to buy those. A lot of those companies are now starting to prefer shared source type licenses.
2) open source advocates that don't like any commercial usage of their software and will actively want to prevent any form of intermingling of closed source and open source components like is common in many commercial projects. This is nominally to protect their freedom. But of course it has consequences in the context of commercial projects that don't want to opensource their proprietary stuff. Whether that is actually true or not for any particular use requires a bit of careful legal scrutiny.
Some places that do license audits (e.g. most banks, insurers, and other large companies that need to be alert to potential legal pitfals) would probably flag anything under this license. Three reasons for this: these licenses are only fine under very specific circumstances and certain combinations of licenses are not compatible. And finally of course these audits and lawyers are expensive. So, the easiest way to stay safe would be a blanket ban on anything with this license. Which is my general attitude towards this license.
Anyway, don't take your advice from random commenters (including me) on hacker news and consult a lawyer when in doubt. Yes that costs money. Alternatively, save some money and just steer clear of this mess.
On the other hand, usually that’s the intention when a project selects AGPL. There’s usually a commercial license you can buy instead (see iText for example).
https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html
Are there any lawyers or legal cases that you know of that have proven this? or at least lawyers who have reviewed it and given a legal opinion?
[0] https://www.microsoft.com/en-us/research/blog/introducing-ga...
In general, projects like Postgresql and other successful open source projects have in common that generally contributors are not coming from a single company. Community diversity is what gives open source projects resilience against corporate shenanigans. Mysql in some form or another will persevere as well. It has survived a lot of this stuff already and it's still there as an open source option.
I use it as a guide to select which things I use. I look for three things in open source tools and libraries that I use: 1) proper licensing (No agpl or shared source nonsense) 2) community diversity (no single companies that can change their mind), 3) active & recent development demonstrating the project is healthy.
Of course the tragedy of individuals like Simon Riggs passing away is that they are so important for the health of these projects. With postgresql, I'm confident that there are others that can step up. But still, he's been very important and it's important to recognize their amazing contributions. The OSS world is full of these type of hero developers and it's what makes using OSS so wonderful. With Redis, that person would be Antirez. And he stepped back from Redis the company some time ago. It will be interesting to see what he does post fork.