Live data from Hacker News

Redis is forked

vickiboykis.com

11–20 of 206 posts

Re: Redis is forked

#11

Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…

I think it is too early to evaluate Terraform/OpenToFu. They're diverging now and it looks like OpenToFu are bringing on some wanted features.

I agree. It has only been a few months since the split. I have noticed more and more uptake of OpenTofu amongst colleagues, and I've personally switched. The thing that makes the difference is what is running on people's laptops, because that's what people will eventually put into prod.

Re: Redis is forked

#12

Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…

>Generally my stance with these forks born from community drama is "wait and see."

They are generally a good thing, save for the poor souls that will end up maintaining a project that was started with them while they were still active. The success of the fork doesn't matter so much as the direction it inevitably pulls the original project.

The io.js drama gave us a huge step forward with NPM once their hand was forced. Hopefully some good ideas come of this too.

Re: Redis is forked

#13

Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…

> people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it

If it wasn't open-source it won't be as popular as it is in the first place, Redis is also using ton of open source software or libraries for free.

Not defending AWS/GCP/Azure, I actually got my software used when i was young by a large company for free (not even a mention- Still using it i think, 5M+ Play Store Downloads), but that is the spirit of open source

Re: Redis is forked

#14
As somebody who pulled down an open source project I find this trope of FOSS losing its way for greed utterly disingenuous.

People need to put food on the table, period. I’ve had people take my work and make more money from it than I have, with no attribution or credit.

Then I pulled it down and got a lot of people asking why it’s no longer free, when I tell them I can sell them a license they don’t even reply.

I care more about my family than your FOSS ideals. End of story.

Re: Redis is forked

#15
If AWS and other cloud providers gave if only 0.1% of the profit they generate out of these open source projects back to the developers we probably wouldn't have this problem. Unfortunately they don't and it's only fair that eventually those developers take it in their own hands. It's not a great situation but it's certainly understandable.

Re: Redis is forked

#16

I thought the author was bringing in genAI for little reason...then I clicked through. For some reason storing vectors and chats is core to Redis' vision of its future. ( https://redis.io/blog/the-future-of-redis/ ) I'm, generally, a mobile dev so I'm not familiar with redis. My handwave-y understanding is its a in-memory key/value DB. I don't understand how that brings anything to the table for genAI. Couldn't the p…

Vector databases aren't for key value retrieval, they're for similarity search. What's that got to do with onnx?

Re: Redis is forked

#17

Changing from an open source license is a kind of tech product spin on enshitification. Even if the product continues to get features and active development, like Oracle poured into MySQL after its acquisition, a database or framework going less open source is still a death knell. The mainstream programmers will move on and use something else. Anything else. Who who has heard that the license can change would now pic…

Pay up or roll your own. Nobody owes you free labor.

Re: Redis is forked

#18

I thought the author was bringing in genAI for little reason...then I clicked through. For some reason storing vectors and chats is core to Redis' vision of its future. ( https://redis.io/blog/the-future-of-redis/ ) I'm, generally, a mobile dev so I'm not familiar with redis. My handwave-y understanding is its a in-memory key/value DB. I don't understand how that brings anything to the table for genAI. Couldn't the p…

Redis will be used for genAI as it's always used: answer queries faster. Users are not interesting in waiting, answers need to be immediate. Plus reducing load on whatever you got behind Redis is a nice bonus.

Re: Redis is forked

#19
post #10

Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…

Best example for a successful fork is gitea. It's so incredible what they have achieved since the fork from gogs

(And then gitea was forked into forgejo, which is used by codeberg, iiuc)

Re: Redis is forked

#20
The post is a little conflicted? It starts by saying he likes redis becasue it was a great fit for his personal vector db he wrote on top of it but then goes on to say he's worried about the future of the company for focusing on ai support, which is what he was already doing with it? I'm not sure I really get the concern about trying to support ai needs though. Atleast it's relevant compared to making changes to a stable kv store for the sake of change.

Are these redis forks just vocal terminally online internet people fighting, like most people don't resell redis and don't care, don't comment or get involved?

Post reply on HN