Related:
Redis is trying to take over the all of the OSS Redis libraries
Redis Inc seeks control over future of Rust redis-rs client library
21–30 of 68 posts
Re: Redis Inc seeks control over future of Rust redis-rs client library
#22I 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"
PE/VC-backed bait-and-switch takeovers of "open source" projects have cost me a significant amount of time and money over the past few years.
My rule of thumb now is that I now consider any project that has a pricing page OR requires copyright assignment/CLA to a for-profit company to be effectively proprietary and just using open source as a marketing technique. That doesn't mean I won't touch it, but like with proprietary software, I'll evaluate it against the risk that the price will probably be jacked up in the future.
Re: Redis Inc seeks control over future of Rust redis-rs client library
#23Seems like this was resolved with Redis Inc backing off prior to the HN post. From @mortensi roughly 4 hours prior to the post: https://github.com/redis-rs/redis-rs/issues/1419#issuecommen...
> Thanks everybody for the feedback. Speaking on behalf of Redis Inc., we want to find a way to collaborate to best support the community and our customers. The objective is to ensure predictable releases for a Rust client library, manage issues and escalations promptly, as well as support the best we have to offer without forking the library and competing with the client library project. After discussing this with @nihohit in this thread and based on the whole conversation, we want to work together. We have already identified initial areas from which we could start.
> We have no issues keeping the project name as it is without a transition to Redis. We also have no problems with continuing to call this library "redis-rs". There is no intention to claim ownership of the client library's name, source code, or the crate’s package registry.
Re: Redis Inc seeks control over future of Rust redis-rs client library
#24I 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 c…
excellent summary (not kidding); thank you for it because i hadn't understood it until what you wrote
Re: Redis Inc seeks control over future of Rust redis-rs client library
#25https://github.com/redis-rs/redis-rs/issues/1419#issuecommen... - looks to be mostly resolved at this point, with Redis Inc. simply going to step up its contributions to the open-source version without taking control.
Thank you antirez, mitsuhiko, and mortensi for working to resolve this amicably!
Re: Redis Inc seeks control over future of Rust redis-rs client library
#26Earlier quoted context omitted.
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).
Microsoft has also been working on one. https://microsoft.github.io/garnet/
Re: Redis Inc seeks control over future of Rust redis-rs client library
#27Seems like this was resolved with Redis Inc backing off prior to the HN post. From @mortensi roughly 4 hours prior to the post: https://github.com/redis-rs/redis-rs/issues/1419#issuecommen... > Thanks everybody for the feedback. Speaking on behalf of Redis Inc., we want to find a way to collaborate to best support the community and our customers. The objective is to ensure predictable releases for a Rust client libra…
Comments are all reasonable and there was no reason for the drama in the first place...
Rust seems to just attract drama sometimes, the other client library owners dealt with the company without blowing up?
Re: Redis Inc seeks control over future of Rust redis-rs client library
#28I 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 c…
> The company also managed to acquire full rights of the Redis trademark and project stewardship from antirez after hiring him
How did that happen? He must have given/sold it to them, right? I remember him making an announcement that he was done with Redis and stepping away from involvement.
Re: Redis Inc seeks control over future of Rust redis-rs client library
#29Earlier quoted context omitted.
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).
Kvrocks is pretty substantially different, from my understanding. It only shares the protocol.
Re: Redis Inc seeks control over future of Rust redis-rs client library
#30Alright gang, from now on, all community projects are named Sider.
Well done, for those that missed it: "Sider" is "Redis" back-wards.