Hacker News Reader

Comment by wg0 | Hacker News Reader

Another wonderful piece of open source software swallowed by corporate warlords. Now expecting an OpenRedis fork soon from AWS?

View on HN

It's the other way around. Mega corps are cut off from leeching on open work.

It's the only sustainable way to have business model around open work.

With pure open source licensing you have asymmetry - where a) you guys implement it b) we sell it, thanks - problem. You cannot run sustainable business around it.

As far as I understand it they want to preserve "open sourceness" for self hosted projects - ie. if you run redis in your docker/vm/k8s, you're fine. But if mega corp clouds are offering managed service, they need to give back a cut from premium they're charging end users.

Nevertheless the leeches will start a big PR campaign about how the creators are evil for wanting a piece of the pie just like they did for Terraform

Redis is also on the the leeches in this case. They have a 500 people company which plans to profit off of hosting Redis and wants to have a competitive advantage by being the only ones who do not have to open source their modifications.

> As far as I understand it they want to preserve "open sourceness" for self hosted projects - ie. if you run redis in your docker/vm/k8s, you're fine. But if mega corp clouds are offering managed service, they need to give back a cut from premium they're charging end users.

I like it and I think this is how open source should work to thrive.

The world would be a very different place if, say, the people that wrote apache httpd felt this way.

I don't know what it would look like, so I won't weigh in on whether or not it would be a good or a bad thing. But it would assuredly be different.

If a webserver were to use this license it would still allow most enterprises to use it as a web server (IIUC) except if you are offering an open proxy service.

All websites and even value-add proxies likely would not be impacted

I think you're underestimating the impact that the webhosting industry had on the popularity of Apache httpd, all of these related ecosystem projects like PHP, MySQL, etc., and even Linux itself. How many small businesses launched because cheap and good webhosting was plentiful? How many developers cut their teeth making web apps that worked on the average cPanel/WHM webhosting provider? The answer to both of these is "A lot. A whole lot."

The butterfly effect would be massive.

I did not think of this, if I understand the license correctly an AGPL webserver used to host third-party websites would only require the ability to download the source of the webserver, while a whit SSPL it would require the ability to download the source for both the infrastructure and the hosted application.

Definitely a different tradeoff that many would not have been confortable in choosing.

by corporate warlords I mean - the ones leeching off the open source work. :)

But now you're open to [Redis] taking you to court saying that your service that uses [Redis] is too similar to “just [Redis]” for you to offer it to anyone else.

Field of use restrictions are a terrible idea, and totally incompatible with “open sourceness”.

If you run cloud providing business that directly competes with Redis Labs with your "Redis on steroids as a service" then you need to enter into licensing agreement with them to share your profit margin, no drama here, don't be a leech and that's where it ends.

If you're running commercial project where you USE redis, not PROVIDE it, you're fine.

Reply on news.ycombinator.com