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

21–30 of 206 posts

Re: Redis is forked

#21

Post by Thev00d00 »

dainiusse wrote: post #6
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 think it is too early to evaluate Terraform/OpenToFu. They're diverging now and it looks like OpenToFu are bringing on some wanted features.

There is no incentive for users of tf to move, consumers are not impacted by the licensing changes.

Opentofu hasn't shipped a 1.7 stable with removed blocks yet, whilst terraform is already on 1.8 with provider functions

Re: Redis is forked

#22

Post by snotrockets »

vdfs wrote: post #13
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…

> 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 Down…

Redis actually has very few external dependencies compared to most modern FOSS:

IIRC, it only need libc and OpenSSL (the latter only if you build TLS) on your system, and provide their forked copies of Jemalloc, LUA, fpconv, HiRedis, Linenoise and Hdr_Histogram.

Re: Redis is forked

#23

Post by stefan_ »

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.

Re: Redis is forked

#26

Post by snotrockets »

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…

> 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 it in a way that doesn't allow such. You can't recall a gift because you don't like how the recipient is using it. Though you are more then welcome not to gift them ever again.

Re: Redis is forked

#27

Post by Comma2976 »

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…

The hyperscalers weren't selling Terraform though, Hashicorp was losing to Terragrunt, Spacelift et al, who had decent to good offerings.

I'd say Elasticsearch is still the comparison to make here for a product that clouds just resold, then again, Redis the company didn't build Redis the software and their latest marketing smells more of VC hawkery than any reasonable pitch

Re: Redis is forked

#28

Post by cube2222 »

Thev00d00 wrote: post #21
dainiusse wrote: post #6

Earlier quoted context omitted.

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.

There is no incentive for users of tf to move, consumers are not impacted by the licensing changes. Opentofu hasn't shipped a 1.7 stable with removed blocks yet, whilst terraform is already on 1.8 with provider functions

Hey, tech lead of the project here!

Just to clarify, provider-defined functions are coming in OpenTofu 1.7, along with e2e state encryption. Generally, I recommend not comparing version numbers of Terraform and OpenTofu post-1.6.

Implementing the e2e state encryption was non-trivial, and we wanted to make sure we get it right, so that's why the release took us a while. We also got a slight additional delay due to needing to handle the C&D letter OpenTofu got from HashiCorp[0], but that's all sorted now.

The beta for 1.7 however is coming out this week, with the stable release planned in the next ~3 weeks.

[0]: https://opentofu.org/blog/our-response-to-hashicorps-cease-a...

Re: Redis is forked

#29

Post by 46Bit »

Thev00d00 wrote: post #21
dainiusse wrote: post #6

Earlier quoted context omitted.

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.

There is no incentive for users of tf to move, consumers are not impacted by the licensing changes. Opentofu hasn't shipped a 1.7 stable with removed blocks yet, whilst terraform is already on 1.8 with provider functions

Anecdotally, I know several teams likely to adopt OpenTofu when state encryption ships https://terrateam.io/blog/opentofu-feature-preview-state-enc...

Re: Redis is forked

#30

Post by starttoaster »

bevekspldnw wrote: post #17
wood_spirit wrote: post #9

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.

Nobody owes you free labor, but it's a world of uncertainty. People don't like uncertainty. Will this labor be priced reasonably, at around the same level that I value it, or will they pull a vmware and ask for my first born?
Post reply on HN