Remix clone Hacker News

new | show | ask | jobs Github

▲

perryizgr8 6 hours ago

What are they hoping to get out of it? Wouldn't this just inconvenience their own users?

▲

a_vanderbilt 5 hours ago | parent [-]

Consolidation of control and brand recognition. As soon as Redis revealed their hostile intentions, forks split off. Valkey seems to be the favored one, and in my direct experience is what projects are using moving forward. If we don't intend to use Redis' commercial services we have no reason to use them given the license fuckery.

Like IBM with Redhat, they tried to overstep their position and exert undue control, so the community rejected their status as BDFL. Now IBM has Rocky and Liberty to deal with, and Redis has Valkey rapidly gaining credibility as the go-to solution. The social contract of FOSS goes both ways, and greed is righteously punished with the loss of power.

▲

theideaofcoffee 5 hours ago | parent | next [-]

This was the obvious play when the original Garantia Data-now-Redis Labs went on their acquisition spree and subsequent buttoning up of the ecosystem via their cloud/hosted enterprise offering even before 2013 and then taking the Redis name for themselves. I believe it was only slowed down because of the community aspect pushing back against the stupid licensing changes of it, otherwise they would have gone full steam into it to get even more control. It's so sad to see a good product like that be hung out on the whims of some scummy leeches.

▲

stult 4 hours ago | parent | prev [-]

I’m sure most of it is trademark preservation. Trademarks are enforce it or lose it.

	▲	toast0 2 hours ago \| parent [-]
		You can enforce by requiring an agreement, and making the terms reasonable enough that an OSS project can agree to them (this isn't entirely easy, but it's not that hard either). Also, there's the thing where these other projects have been using the name since forever, so there's already a history of non-enforcement.