141–150 of 815 posts
After what Mullenweg has pulled, in the era of Blogging CEOs I have to be cynical. Valkey.
Heh! While I appreciate what you're saying, I see this as the opposite of WordPress. It's basically a CEO saying oops, we messed up, let's fix this, which is fundamentally different than doubling down and ending up in court.
,,for companies rooted in open source, it has posed a fundamental challenge: how do you keep innovating and investing in OSS projects when cloud providers reap the profits and control the infrastructure without proportional contributions back to the projects that they exploit?'' I don't see any exploitation happening. As DHH said, the main reason engineers open source their work is to give a gift to the world.
Earlier quoted context omitted.
I don't see how it's worse? https://github.com/microsoft/garnet/blob/main/LICENSE It's MIT licensed?
Microsoft has a habit of "fake" open source. Particularly on Github. By "fake", I mean Microsoft largely treats their Open Source codebases like they are closed-source, in-house proprietary codebases that they happen to let members of the public look at. They'll accept a PR once in a while, but mostly it appears Issues and PR's are used as a free alternative to UserVoice. Every decision is made behind closed doors (p…
The only way this remains open source forever is to accept AGPL-only licensed patches.
[1]: https://github.com/redis/redis/blob/d65102861f51af48241f607a...
Earlier quoted context omitted.
At the very least you have to validate everything that touches redis, which means finding everything that touches redis. Internal tools and docs need to be updated. And who knows if someone adopted post-fork features? If this is a production system that supports the core business, hundreds of hours seems pretty reasonable. For a small operation that can afford to YOLO it, sure, it should be pretty easy.
But why are they spending any time switching away from Redis at all unless they are a hosting provider offering Redis-as-a-service? I wasn't aware the license had any negative affect on private internal use.
Our company made the switch over to Valkey, and we've invested hundreds of engineering hours into it already. I don't see us switching back at this point especially when it's clear Redis could easily pull the bait-and-switch again.
Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?
Now consider a no-down-time migration. How long do you think that'll take to engineer and execute?
Earlier quoted context omitted.
Amazon really encourages valkey in the elasticache dashboard. There's a banner advertising lower prices and it's listed first in the dropdown when you go to create one. Default settings do have power.
Sure, but the impact of new customers and their decisions take a long time before they impact net statistics. All evidence I can find, regardless of domain or context, suggests Redis vs. valkey marketshare is something around a 99%/1% difference.
What evidence did you find?
Earlier quoted context omitted.
Heh! While I appreciate what you're saying, I see this as the opposite of WordPress. It's basically a CEO saying oops, we messed up, let's fix this, which is fundamentally different than doubling down and ending up in court.
Oh, I agree... I want to be wrong
Earlier quoted context omitted.
AWS and GCP offer valkey-based versions of products that are typically based on Redis, but those versions are currently, generally, preview-grade, and statistically zero customers are using them. They still offer the original, Redis-based versions of those products, which, statistically, 100% of their customers are using.
> and statistically zero customers are using them You've said this twice now, but not provided any data or even a hand-wave to a possible source so that others could go get the data and look at it. If it's statistically something, where are the stats?
Our company made the switch over to Valkey, and we've invested hundreds of engineering hours into it already. I don't see us switching back at this point especially when it's clear Redis could easily pull the bait-and-switch again.
Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?