Matt, you say that you've had no other reports and this is the only claim on the Internet.
That's not true. You have users on the support forums reporting issues with SCF.
"this has caused an incident requiring unschedule maintenance on a weekend. I use this plugin on a couple hundred sites I help maintain, so this has been a very bad experience "
The complaint says Matt has been lying to the IRS and self-dealing. Is this a legal maneuver by Rachel Kassabian to have Matt lose the WordPress trademark?
Why is it sad? If he is self-dealing between wordpress.org and Automattic, that's a big no-no. It sure looks from his comments here like he sees the two as one entity.
Also, the man outright said "use 'WP' since we think 'WP' is generic" and then cried "brand confusion" years later. If you want to avoid brand confusion, maybe don't tell people they can use your trademark?
You make it sound like it's a black eye against Kassabian.
In fact, many people believe that absolutely, if he has been lying to the IRS and self-dealing his way into a $400M net worth, then absolutely he deserves to lose the license to that trademark.
I think it was explained elsewhere, but Automattic has the commercial trademark rights, partly because they owned the trademark before the WP foundation was created.
* When the pendulum has swung back from NoSQL, MySQL was in a weird place due to Oracle.
* OSS project and foundation not dominated by any particular company means that startups are willing to bet on it. In turn, these startups bring more tools, extensions, and attention to Postgres.
* The open wire protocol, with multiple existing implementations, means that if your application depends on Postgres, you will have plenty of options going forward.
* The extension ecosystem is working because extensions can do almost anything (create types, indexes, functions, etc.). And now pgrx and pgzx open up to writing extensions in Rust and Zig.
My guess was also the ease of building safe extensions along with numerous vector and time series extensions, and it's recently improved replication capabilities.
We switched from MySQL at work probably ~5 years ago. Half following the hype, and half because we had a couple instances of DB corruption on MySQL and weren't ever able to determine the cause.
Postgres has been great, and it's free, so we roll it for almost everything now. I say almost everything because sometimes SQLite is a better fit-- when a DB is only a few MB on an internal app etc.
