Earlier quoted context omitted.
Embrace, Extend, Extinguish is from an era where Open Source wasn't the default for infrastructure. I don't know how you can extinguish something that's MIT licensed and has a million copies around the world.
I've read at least several stories from this era like AppGet's https://medium.com/@keivan/the-day-appget-died-e9a5c96c8b22 I wouldn't trust Microsoft near my open source code base in 3 centuries They can extinguish it by just stealing all the code, and using their bigger marketplace advantage to become the defacto standard.
Redis is open source again
201–210 of 815 posts
Re: Redis is open source again
#202Earlier quoted context omitted.
I've read at least several stories from this era like AppGet's https://medium.com/@keivan/the-day-appget-died-e9a5c96c8b22 I wouldn't trust Microsoft near my open source code base in 3 centuries They can extinguish it by just stealing all the code, and using their bigger marketplace advantage to become the defacto standard.
I'm fairly impressed Microsoft managed not to name their Redis competitor "Cache", just to pollute the keyspace like they do with so many of their other products.
Re: Redis is open source again
#203Earlier quoted context omitted.
Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?
I can easily see this for a midsize company. While it's likely an easy process to drop in valkey, creating the new instances, migrating apps to those new instances, and making sure there's not some hidden regression (even though it's "drop in") all takes time. At a minimum, 1 or 2 hours per app optimistically. My company has hundreds of apps (hurray microservices). That's where "hundreds of hours" seems pretty reason…
Re: Redis is open source again
#204Earlier quoted context omitted.
We need to stop taking the OSI or FSF's positions on anything as particularly valuable. The OSI is captured entirely by corporate sponsors. Amazon was paying a full-time salary a year to the OSI when the SSPL issue happened, the OSI had no ability to take a moral pro-labor stance without crippling their own operations. They still do not meaningfully answer to individual users: The OSI recently refused to disclose who…
Which part of their explanation for rejecting it do you specifically disagree with?
The OSI then strays into a lot of nonsense that demonstrates just how bought and paid for they are, such as "the understanding that their work was going towards the greater good", like apparently... being used by a company which does not open source it's platform and treats its employees so poorly they have to pee in bottles. And of course, they immediately claim that "now... contributions are embedded in a proprietary product" because of course, the OSI believes they own the term and definition of open source, and that everything they don't agree with is inherently "proprietary".
And then of course, they suggest "relicensing is not evidence of any failure of the open source licensing model" even though it is very clear that businesses being unable to survive producing open source is kinda big flaw in the goal of promoting the public software commons. (Taking it a step further, if the FSF argues free software is a moral imperative, not fixing this is outright immoral.)
Re: Redis is open source again
#205One of the big things I love about Redis is that it’s become this tool for me to learn new techniques and explore data. Like, the new vector sets feature has let me really explore dense vectors and custom search and taxonomy mapping and all sorts of areas that seemed like a high barrier to entry for me, but now I’m just streaming stuff into llama.cpp with an embedding model and storing it in Redis and being able to d…
Re: Redis is open source again
#206Earlier quoted context omitted.
> 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?
[flagged]
We've already completed migrating several large production clusters and I can confidently say that the migration had been pretty smooth and seamless.
Valkey is certainly production ready (at least on AWS it is). The team is looking forward to expedite and complete the migration
Re: Redis is open source again
#207Lots of cynical takes in this thread - and I get it, there isn't a guarantee they won't relicense again in the future (they have a CLA that would let them) and people feel betrayed by the last license change. I think we should celebrate this anyway. It's a smart decision, it's what the community wanted to happen and it would be great if other companies with janky licenses could see "Redis relicensed to open source an…
Re: Redis is open source again
#208Earlier quoted context omitted.
Microsoft made one called Garnet, I wouldn't say its a fork though, its basically compatible with Redis and implemented mostly in C#. It supports the RESP wire protocol from Redis for ease of compatibility. https://github.com/microsoft/garnet
Garnet fascinates me. Their benchmarks even claim that it is better than Redis and also Dragonfly. Are there any papers or write ups explaining what makes Garnet fast? (I do know its based on FASTER)
It struggles a bit on certain types of workloads like hot keys, think heavy hitting a single sorted set. It's a cool architecture.
Re: Redis is open source again
#209Re: Redis is open source again
#210I'm curious whether the community will trust Redis-the-company again after this, or if they'll choose to stick with Valkey. The other concern is at least some big company legal departments are wary of AGPL software, which makes Valkey, still BSD, more attractive to them. Edit: Regardless, thank you and the rest of the folks inside Redis for pushing to bring this back to OSS!
Statistically nobody is using valkey.