On another topic:
> The Varnish Cache FOSS software was initiated and sponsored by the Norvegian newspaper Verdens Gang. They hired a company called “Linpro” to handle the logistics and me to write the code.
> From Linpro grew the company Varnish Software
> IP-Lawyers still insist that Varnish Software owns the Varnish Cache name
Consultants came in a just assumed the IP? It sounds like a pretty complicated cross-border ordeal, but that is still quite a leap.
> Varnish Cache is a distribution of the open-source Vinyl Cache project, made for the modern cloud: ready for Kubernetes, with built-in TLS support, and a long-term-support release cadence with extra modules and tooling layered on top.
> I will also state for the record, that there are no hard feelings between Varnish Software and the FOSS project.
I wonder if that is still the case now. (this article is fairly diplomatically written, but I'd imagine it must be pretty frustrating)
[0] https://vinyl-cache.org/organization/20-years.html#years
But if FOSS is deeply encoded into your DNA, you become pretty protective once you realize your project may become extinct sometimes in the future.
My, Maria, and Max are his kids. There is MaxScale which is a L7 SQL proxy/loadbalancer
That said, it seems to be a common point of confusion among FOSS die-hards, but still super unfortunate to see it repeated in this context!
Given that MariaDB the company is now owned by a private equity firm, I doubt it's going to get better.
I'm sure for some shops this will drive them to pay for the same feature in MariaDB cluster, but I'm more likely to just transition to MySQL Group Replication.
This is my whole point about MariaDB - they are steadily making their OSS software completely dependent on the company (paid) versions for anything beyond toy scale.
Oracle has also been guilty of locking modern table stakes behind the MySQL Enterprise / Heatwave pay gate, such as vector indexes and JS stored procedures. And while they've recently announced more of this stuff will move to FOSS soon, at the same time their response rate to new bug reports has become worse than ever before, which is deeply worrying.
And a couple days ago Oracle announced that they're nonsensically changing their MySQL versioning/LTS naming yet again. So now the way you identify an LTS is "major version is an even-numbered last two digits of a year, while minor version is exactly 4 to represent LTS releases always being in April." So for example MySQL 28.4 will be LTS, but 28.7 and 28.10 are not. But prior to this, 9.7 and 8.4 are LTS, and 8.0 was de facto LTS but now EOL. It's bizarre. I wish I was joking!
This continues the faulty line of thinking that open source is just for hobby-level projects or early startup throwaway infrastructure. So many open-core models rely on this falsehood to rationalize their decisions. It should be possible to run large-scale important Internet things on Open Source code, too, for a variety of reasons.
How so? I don't understand your comment at all. A huge chunk of the world's economy runs on async replication in FOSS MySQL/MariaDB, my whole point was that you literally don't need Galera to do that.
So, the stuff that basically appeals to people chasing the AI dragon, and has zero practical use for 99.999% of developers making real products?
> I wish I was joking!
I wish I could care even a little bit about such minutiae.
And how is it "minutiae" to be able to figure out "is my database version actually supported"? This is the fourth versioning scheme they've used in less than a decade, that's a bit nuts I think.
> And how is it "minutiae" to be able to figure out "is my database version actually supported"?
Remembering "8.4", "9.7" and ".4" just doesn't seem like a particularly big deal to me. The number* has only changed 3 times in the last 10 years.
As for the versioning, it's a nightmare for third party vendors like me, because it will absolutely increase the number of companies who are unintentionally running unsupported non-LTS "innovation" releases because they can't keep all these versioning changes straight. The major-version only changed 3 times in the past decade because 8.0 was "evergreen" for most of that time, which was also not a good strategy, yet the most obvious solution (SemVer) is always ignored by Oracle in favor of more confusing alternatives.