341–350 of 472 posts
Earlier quoted context omitted.
It's possible to hold both positions at the same time.
In the world of legal consequences it is not. Or please explain.
One simply can't admit that they both were doing a valid thing
I'm really interested in this bit: "the fracture with the community is not about licensing, or at least it’s not mainly about licensing" I wish he'd elaborated a bit more on what he thought it was about. My understanding is that it's 100% about the license. That's certainly why I'll reach for valkey instead of redis next time I need it. That's also what I've heard from everyone else in a similar position. What else w…
I'm really interested in this bit: "the fracture with the community is not about licensing, or at least it’s not mainly about licensing" I wish he'd elaborated a bit more on what he thought it was about. My understanding is that it's 100% about the license. That's certainly why I'll reach for valkey instead of redis next time I need it. That's also what I've heard from everyone else in a similar position. What else w…
something is off in redis execution
hope with this guy comes back it improves!
That vector sets design outlined towards the end of the article is delightful - it's exactly the kind of API design I appreciate from Redis over the years: simple, elegant and feels obviously correct to me.
Earlier quoted context omitted.
With open-source software, a license is as much a social contract as it is a legal one. People contribute because they want to be part of a community building something which is beneficial to everyone . Everyone contributes where they can, and in turn takes what they need. Redis Ltd. broke the social contract. They decided that the short-term profitability of the company was more important than the project as a whole…
Open source is a gift economy. Receiving a gift does not form a social contract that entitles you to future gifts. It is not a "rug pull" for someone to stop giving you gifts. The old versions of Redis are yours for all time. No one can take that away from you. In fact, Redis is still giving you gifts to this day, just with a different wrapping. The new license seems perfectly reasonable, given how much companies lik…
Earlier quoted context omitted.
> Many people had contributed their efforts to the Redis project for free It's worth noting that the bulk of the code was written by antirez with only ~12 others exceeding 100+ commits [1]. And if you continue scrolling the number of commits-per-user drops off fast. It's striking given how famous the project is. [1] https://github.com/redis/redis/graphs/contributors
It goes far beyond the actual codebase to the long tail of supporting projects, conference talks, blog posts, etc
I love that Antirez is on Bluesky and not X. We should all turn off X and migrate out of that toxic platform.
For me, the license change upset me mainly for two reasons: 1. Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc - and when they did that it was under the understanding that project would remain under the same open source license. It honestly felt like a betrayal of trust. 2. From a purely selfish point…
> It used to be that you could pick an open source project and build a business on it and expect that the project would stay available to you under those well understood terms. I'm not familiar with what's happening in this Redis licence change. But if it was Open Source at version N, and you built your business (or stack, etc) on top of that, N will remain forever available to you as FLOSS, not? Is the problem maybe…
They see this as "rug pulling". I think developers need to do a lot more of that for things to change.
I'm really interested in this bit: "the fracture with the community is not about licensing, or at least it’s not mainly about licensing" I wish he'd elaborated a bit more on what he thought it was about. My understanding is that it's 100% about the license. That's certainly why I'll reach for valkey instead of redis next time I need it. That's also what I've heard from everyone else in a similar position. What else w…
AGPL only slightly prevents this by forcing them to share their changes to the source. And usually this is not very useful to the community, anyway. And very little effort. And the same people scream it's an evil license. They want free (as in beer) stuff forever and it's not just the source code. It's very ungrateful of them.