Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Redis is forked

vickiboykis.com

Post reply on HN
Print view View original

41–50 of 206 posts

Re: Redis is forked

#41

Post by cube2222 »

hnthrowaway6543 wrote: post #4

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…

Hey, tech lead of OpenTofu here!

I might be in a bubble of course, but from what I've seen, I've been positively surprised by the uptake of OpenTofu so far!

I do also expect OpenTofu 1.7 to be more interesting for people to migrate to, as it'll include a bunch of OpenTofu-exclusives.

Re: Redis is forked

#42

Post by styfle »

hnthrowaway6543 wrote: post #4

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…

Don’t forget the Node.js and io.js fork. That’s one where the fork basically became the blessed branch and the two communities merged back together.

Re: Redis is forked

#43

Post by lenerdenator »

slashdev wrote: post #32
snotrockets wrote: post #26

Earlier quoted context omitted.

> Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it, making tens of millions of dollars per day in the process. I can't really blame them. I won't blame them for regretting their past actions, but I hope the lesson would be learned: if you want to put limitation on the use of your software, you shouldn't have licensed…

With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. OSI Open-source business models…

They're not dead, just mostly dead.

You can probably set up a decent privately-funded venture to deal in OSI software. The problem comes (as it always does) when the founders think they're the reincarnation of Steve Jobs and deserve a nine-or-ten-figure net worth for making a few nice, but ultimately not earth-shattering, software tools. Then they have to enshittify to get ready for the IPO.

Re: Redis is forked

#44

Post by hn72774 »

I had a bad experience with redis salespersons sending me unsolicited calendar invites. They were promptly deleted and marked as spam.

You are pushing away potential customers with this behavior.

Re: Redis is forked

#45

Post by merb »

stefan_ wrote: post #23
hnthrowaway6543 wrote: post #4

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 remember when we had the libav fork. Turns out 10 bickering idiots pronouncing the freedom revolution were ultimately not half as productive as one Michael Niedermayer.

tbf, ffmpeg‘s api and thus libav is so obscure that it would be impossible to fork it and create a nice looking api, without bothering people.

I vaguely remember the news about the Microsoft guy that was called out on twitter and I’ve read the issue and looked at some cli/api parameters and was stunned. So much possible flags. I hope that I will never need to deal with it.

But still kudos for all the maintainers. It works and has probably support for all codes and all options of these codes.

Re: Redis is forked

#46

Post by all2 »

esafak wrote: post #16
refulgentis wrote: post #3

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?

Onnx allows arbitrary bundling and execution of ML models.. so maybe something to with the "run it local and private"?

Re: Redis is forked

#47

Post by snotrockets »

laurent123456 wrote: post #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.

Disregarding the question of if the CSP compete fairly with providers of open source SaaS, your math is broken:

AWS revenue is about $90.76B, though most of it isn't from Redis, I'd assume. But let's be generous, and assume 10% of that is. So about $10mm. For the recent version, Redis-the-company contributions to Redis-the-software were less than third of the code base, so let's say they get $4mm. That's very little revenue for a company that has a valuation of over $2B.

Re: Redis is forked

#49

Post by Pet_Ant »

slashdev wrote: post #32
snotrockets wrote: post #26

Earlier quoted context omitted.

> Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it, making tens of millions of dollars per day in the process. I can't really blame them. I won't blame them for regretting their past actions, but I hope the lesson would be learned: if you want to put limitation on the use of your software, you shouldn't have licensed…

With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. OSI Open-source business models…

> Don't use OSI open-source unless it's entirely a labor of love that you're giving away free.

Well, know what your secret sauce is. I think performance is really the best differentiator. Make a fully behaviourally compatible (maybe not bug for bug) version available and then sell a proprietary faster version.

Think an compiler that doesn't due any optimisation and outputs naive code. You know have a useful OSI project, and a clear value add, and a clear boundary between the two.

This is really applicable for databases, and it still leaves you with something useful for learning small projects, and for developers to run locally on their own machines.

Post reply on HN