Interesting to see SQL Server not listed here, am curious whether it didn't have enough signal, or suffered from being a two-word product, with "SQL" being far too generic on its own.
replies(2):
Something that I’ve been thinking about a lot recently is that all of the proprietary vendors are quietly strangling their flagship products.
Free and open source database engines were always “nipping at their heels” but weren’t a serious threat for decades. Only other proprietary engines were.
Now that PostgreSQL has more features than SQL Server and better performance, it’s a serious competitor.
But Microsoft is holding MSSQL’s face under water with core-based licensing. It means that per dollar you get dozens of times less compute available for your data than with open-source systems. That ratio is growing exponentially, because they haven’t redone their pricing in… ever.
Oracle and DB2 are being similarly choked off at the same rate, so looking left and right at their direct competition their respective product managers haven’t noticed the problem, which is akin to Fuji and Kodak raising film prices in lockstep just as digital photography is taking off.
We’re entering the era of “kilocores”: single servers becoming available that have over a thousand cores. You can’t imagine what per-core licensing costs for something like that!
PS: I saw a similar dynamic play out in the network space with load balancers and “web accelerators” like NetScaler sold “by bandwidth” with a starter SKU as small as 2 Mbps. I kept trying to politely explain to the reps that the smallest cloud VMs can cheerfully put out 10 Gbps, and hence their product is a 500x decelerator. They eventually listened to someone and made it bandwidth-unlimited. Too late. Everyone uses NGINX now.
Proprietary compilers and developer tooling were similarly strangled, and have been completely replaced by free/open tools in all but a few niche areas such as embedded, hard realtime, and circuit design.