Live data from Hacker News

Redict 7.3.0, a copyleft fork of Redis, is now available

redict.io

31–40 of 178 posts

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#31
post #19
post #3

If you have a commercial use-case, there is also a non copyleft fork available here https://www.linuxfoundation.org/press/linux-foundation-launc...

Most commercial projects can safely use any of the Redis forks, whether Redis itself, Redict or Valkey. For Redict, you have to provide the source code of Redict - and Redict only! - in the case that you distribute it to customers. Redis has harsher terms, but only if you provide Redis-as-a-service. If you aren't a cloud provider and you don't modify the code of your chosen Redis variant, this is all a big nothingbur…

> If you aren't a cloud provider and you don't modify the code of your chosen Redis variant,

Or get hosted redis services from someone other than Redis Labs. That isn't fearmongering about the SSPL, it is literally the point of the SSPL.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#32

Earlier quoted context omitted.

Redis Labs didn't start Redis, they didn't contribute most of the code. They just own the trademark. They have about as much right to extract money from AWS and Google for Redis as I have, all they are doing is that they are hijacking an open source project to make themselves rich. They're not a victim of the cloud providers, they are a leech trying to make a score while fucking over all the other contributors to Red…

Hmm, so anyone can just start a company with the name of an open source project and try to monetise it? Like someone could start e.g. "Rust Labs" and sell a commercial version of Rust? I don't know much about the genesis of Redis or Redis Labs, who key people and dates are, etc. I guess this obfuscation is part of the problem.

> Like someone could start e.g. "Rust Labs" and sell a commercial version of Rust?

No, because the Rust trademark guidelines prohibit that (https://foundation.rust-lang.org/policies/logo-policy-and-me...)

In Redis Labs case, they acquired the Redis trademark from the original author, who they employed for a few years after the project was well established.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#33
post #19
post #3

If you have a commercial use-case, there is also a non copyleft fork available here https://www.linuxfoundation.org/press/linux-foundation-launc...

Most commercial projects can safely use any of the Redis forks, whether Redis itself, Redict or Valkey. For Redict, you have to provide the source code of Redict - and Redict only! - in the case that you distribute it to customers. Redis has harsher terms, but only if you provide Redis-as-a-service. If you aren't a cloud provider and you don't modify the code of your chosen Redis variant, this is all a big nothingbur…

Open source seems to be doing fine without the clarity. Even fields that have nothing to do with software are adopting the mindset. The movement only gains in steam

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#34
I mostly use Redis in combination with RedisJSON, and RedisInsight is a nice way to check what data is stored. I'm only using it for a handful of small documents which mirror the state of some devices.

These options (Redict, Valkey) don't seem to support JSON as a data type, so I'd like to know if there is some server specifically made for dealing with JSON documents. Something like a very lightweight MongoDB server which can be managed via a browser and where the data can be inserted/updated/removed via HTTP calls.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#35

Earlier quoted context omitted.

Redis Labs didn't start Redis, they didn't contribute most of the code. They just own the trademark. They have about as much right to extract money from AWS and Google for Redis as I have, all they are doing is that they are hijacking an open source project to make themselves rich. They're not a victim of the cloud providers, they are a leech trying to make a score while fucking over all the other contributors to Red…

Hmm, so anyone can just start a company with the name of an open source project and try to monetise it? Like someone could start e.g. "Rust Labs" and sell a commercial version of Rust? I don't know much about the genesis of Redis or Redis Labs, who key people and dates are, etc. I guess this obfuscation is part of the problem.

Not really. As mentioned in the article, Redis has a Contributor License Agreement [0] that you have to sign if you contribute to Redis codebase, which basically gives the company behind it ownership behind everyone's contributions:

    You grant to Redis and to the recipients of the software distributed by Redis a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contribution and such derivative works.
Usually, projects don't have such agreements. E.g. Linux, the kernel, would have a hard time re-licensing under different license, because of how many people actually hold the copyright to the code they contributed, and would have to agree beforehand.

[0] https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#36

Earlier quoted context omitted.

Redis Labs didn't start Redis, they didn't contribute most of the code. They just own the trademark. They have about as much right to extract money from AWS and Google for Redis as I have, all they are doing is that they are hijacking an open source project to make themselves rich. They're not a victim of the cloud providers, they are a leech trying to make a score while fucking over all the other contributors to Red…

Hmm, so anyone can just start a company with the name of an open source project and try to monetise it? Like someone could start e.g. "Rust Labs" and sell a commercial version of Rust? I don't know much about the genesis of Redis or Redis Labs, who key people and dates are, etc. I guess this obfuscation is part of the problem.

Redis Labs acquired the trademark from the original owner.

Nobody could start "Rust Labs" without the agreement of the Rust Foundation, because they own the Rust trademark.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#37
post #26

Earlier quoted context omitted.

People are upset because Redis is not open source anymore. That is all.

Is this like a Richard Stallman ideological thing? (EDIT: Genuine question - I'm trying to understand if this is a license purity issue or something else).

People like having choice. The SSPL provides less choice than open source licenses. It came about because users were utilising their choice in way the project leaders didn't like, because they didn't directly financially benefit from it. But without that choice, arguably Redis would not have reached where it is today.

If it had launched as some proprietary single-vendor cloud service, people would have kept using memcached, or their relational DB or whatever for a lot of Redis use cases where it might be nice, but not essential improvements over the competition.

So it's shutting the door behind them, accusing the users of taking advantage of the very thing that let Redis get to where they are today. (Especially so for Redis, where Redis Labs started as just another hosted provider unassociated with the open source projects)

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#38
post #34

I mostly use Redis in combination with RedisJSON, and RedisInsight is a nice way to check what data is stored. I'm only using it for a handful of small documents which mirror the state of some devices. These options (Redict, Valkey) don't seem to support JSON as a data type, so I'd like to know if there is some server specifically made for dealing with JSON documents. Something like a very lightweight MongoDB server…

Redict is binary compatible with Redis Modules, including RedisJSON, out of the box, so you can keep using it no problem.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#39
post #34

I mostly use Redis in combination with RedisJSON, and RedisInsight is a nice way to check what data is stored. I'm only using it for a handful of small documents which mirror the state of some devices. These options (Redict, Valkey) don't seem to support JSON as a data type, so I'd like to know if there is some server specifically made for dealing with JSON documents. Something like a very lightweight MongoDB server…

Lightweight is your problem here, I think, but I've used CouchDB successfully in similar situations. However, its not in-memory like Redis is.

Re: Redict 7.3.0, a copyleft fork of Redis, is now available

#40
post #13
post #9

Time will tell if the version on Codeberg ( https://codeberg.org/redict/redict ) can compete with the fork on Github ( https://github.com/valkey-io/valkey ) in terms of visibility and contributions.

Valkey is under the Linux foundation umbrella, and I assume will be developed by the same people who were previously making redis. I could not find who is behind predict.

It's worth noting that the Linux Foundation is a commercial consortium and the companies behind Valkey contribute over $1M to its annual budget.
Post reply on HN