Remix clone Hacker News

Seems 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.

▲

tayo42 8 hours ago | parent [-]

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?

▲

wongarsu 8 hours ago | parent | next [-]

If we take the maintainer by his word (and I don't see why we shouldn't) then this was very necessary drama that caused Redis Inc to back off.

> the other client library owners dealt with the company without blowing up

A lot of the other client libraries are already under the control of Redis Inc. The Python client, one of the popular Java clients, the Go client and the nodejs package all live in the Redis Inc Github organization.

▲

the_mitsuhiko 8 hours ago | parent | prev [-]

> Comments are all reasonable and there was no reason for the drama in the first place...

As the author of that issue I'm assuming if there was drama, then it was up to me. However I did not intend on causing one, but to discuss this issue with active maintainers of the crate as well as to understand to which degree valkey support is needed by users for the crate.

That this has created a discourse that goes beyond that was not intended.

▲

tayo42 8 hours ago | parent [-]

> That this has created a discourse that goes beyond that was not intended.

I think the thing started off fine and reasonable, but if you go down the comments it takes a turn towards cynical and antagonistic where people are assuming the worst. Which is basically the point of my comment, rust related things seems to have these weird blow ups.

Some quotes

> Redis team has the required Rust proficiency, nor that they actually care about maintaining this crate

> Concepts of a plan eh?

> Of course they don't have a list of missing features, it's not about features. It's about taking control of a ecosystem that's collasping under them because of widly percieved-as shady license rug pulling.

In bold too

> What you care about is your customers, not the community or any contributors.

Then there's headlines like

> Redis Inc seeks control over Rust Redis-rs library, talk of trademark concerns

Its overall inflammatory, when the intention from the emails shown seem fine and the goals seem clear.

	▲	the_mitsuhiko 7 hours ago \| parent [-]
		Unfortunately ever since the relicensing the situation in the Redis community is loaded. I have seen discussions in other repositories around Valkey and the discourse is not much different.