Live data from Hacker News

Redis Inc seeks control over future of Rust redis-rs client library

devclass.com

11–20 of 68 posts

Re: Redis Inc seeks control over future of Rust redis-rs client library

#11
post #2

I have yet to hear a single positive story about this Redis Inc... it's like a giant company full of only assholes. Story after story is just "wow, these people all suck"

They have some of the same people from the elastic license debacle so this makes sense.

Re: Redis Inc seeks control over future of Rust redis-rs client library

#12

My theory is Redis is trying to take control over all popular libraries that interface with it so it can break protocol level compatibility to force vendor lock-in

That would push everyone to valkey. They want to add proprietary features supported only by their server and client. That's the extend part of "embrace, extend, extinguish".

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: Redis Inc seeks control over future of Rust redis-rs client library

#14
post #2

I have yet to hear a single positive story about this Redis Inc... it's like a giant company full of only assholes. Story after story is just "wow, these people all suck"

Redis the project was essentially taken over by a company that had nothing to do with its development.

Salvatore Sanfilippo (antirez) started Redis and developed it by himself from 2009 to 2015, gaining massive popularity and building a large community in the process. It was FOSS the entire time.

A separate VC-backed company called Garantia Data used to make money by offering a hosted version of Redis. That company changed its name to Redis Labs in 2014 (and eventually just Redis), likely themselves violating antirez's Redis trademark at the time.

They then hired antirez in 2015 and started officially sponsoring the project.

From there began a slow transformation of Redis from a community run FOSS project to a proprietary locked down service. The company also managed to acquire full rights of the Redis trademark and project stewardship from antirez after hiring him and then finally kicked him out in 2020.

Re: Redis Inc seeks control over future of Rust redis-rs client library

#15
post #2

I have yet to hear a single positive story about this Redis Inc... it's like a giant company full of only assholes. Story after story is just "wow, these people all suck"

I agree. At the same time, they're just 'doing their job' working at a for-profit company controlling the brand of open-source (core?) software.

Yes, you can simultaneously condemn individual behavior and the system that incentivizes it. Both are bad in this case.

Re: Redis Inc seeks control over future of Rust redis-rs client library

#16

My theory is Redis is trying to take control over all popular libraries that interface with it so it can break protocol level compatibility to force vendor lock-in

Are there many redis drop-ins alternatives?

Valkey is the fork/drop-in replacement from the Linux Foundation.

Re: Redis Inc seeks control over future of Rust redis-rs client library

#17
post #2

I have yet to hear a single positive story about this Redis Inc... it's like a giant company full of only assholes. Story after story is just "wow, these people all suck"

Shame because I remember the original author being quite well regarded on places like here and Reddit.

He still is

Re: Redis Inc seeks control over future of Rust redis-rs client library

#18

My theory is Redis is trying to take control over all popular libraries that interface with it so it can break protocol level compatibility to force vendor lock-in

Are there many redis drop-ins alternatives?

Valkey, dragonfly, kvrocks are all protocol-compatible and mostly drop-in replacements for upstream Redis.

If you want something hosted/managed, there’s Upstash Redis (though I reckon they’ll soon have to change the name of that offering).

Re: Redis Inc seeks control over future of Rust redis-rs client library

#20
post #12

My theory is Redis is trying to take control over all popular libraries that interface with it so it can break protocol level compatibility to force vendor lock-in

That would push everyone to valkey. They want to add proprietary features supported only by their server and client. That's the extend part of "embrace, extend, extinguish". https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

All of this drama is already doing that.
Post reply on HN