It will stay free and you can read the source code and change it.
BUT: Amazon, Google and Microsoft (et al) will have to pay if they offer Redis as part of their cloud.
Seems fair and any article not giving a voice to those being reported on is trash. Here you go, though:
Under the new license, CLOUD SERVICE PROVIDERS hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge.
https://redis.com/blog/redis-adopts-dual-source-available-li...
I predict most forks will go nowhere because the success of a fork requires developers to contribute to it. In most cases the forks are being driven by people who just want free stuff and are angry they can't be subsidized anymore. They don't want to actually do any work.
Open source is not about just leeching free stuff. It's supposed to be a gift economy where you give back either directly or indirectly by promoting, educating, or donating. The F in FOSS is supposed to stand for Freedom not Free-as-in-beer.
A full revolt is in progress against the entire SaaS enterprise leeching off open source. Larger often business backed projects like this changing to source available licenses is the most visible manifestation, but I also see more and more indie devs using licenses like the AGPL or not open sourcing at all.
Open source will die as anything but a dumping strategy by mega-corps to crush competition if we don't deal with this. The OSI is fully captured by companies that benefit from the status quo, so I don't see them doing anything about it.
That code is now untouchable. Open, I can use it. Now that I can read it but not use it, if I accidentally reproduce it there’s a case for me having stole it. If it were fully closed, there’s no case.
Very little good comes from non-open source you can just happen to read.
> Now that I can read it but not use it, if I accidentally reproduce it there’s a case for me having stole it
In the decades of existence of GPL-ed software has there even been such a case? I see this point regurgitated time and time again but no concrete examples are ever provided. Seems a bit like anti-OSS FUD.
No, but famously early IBM clones had to do clean-room reverse engineering of bootloaders and other ancillary code to produce compatible designs.
IBM was able to legally annihilate anyone who ever saw the source code or read technical documents on these designs, but the people who made sure they didn't were able to defend their designs in court.
If you've worked in IP-heavy fields (my experience is with video codecs) you will also see strict guidance to not read patents in your day-to-day.
My understanding is that it is only true for Redis versions post licence change _and_ produced by Redis the company. The amazons of the world can still take a BSD version of Redis and host it for money, they can even start maintaining forks under BSD or other licenses. The gamble from the Redis Co here is that newer versions provide enough additional value for customers to either pay them directly or amazons to provide it as a service in their clouds and pay money to Redis the company as per the licensing agreements.
I see what you’re saying, but I think there’s a moral argument to be made for wanting code to be open source, but for humans only. Contrary to what law says, corporations are not people.
The contributors likely feel like their altruism is being exploited by mega corporations who are looking to harvest free labor. I sure wouldn’t want to work on a project if that’s how I perceived my users. But that doesn’t diminish their desire to provide a code base that anyone can use, learn from, modify, etc.
You or I, the HN readers, may use Redis to power our personal instance of Firefly III or whatever, running in our home lab, but the average _person_ has no need of Redis so for the purposes of this discourse this is a negligible factor.
Typical contributor to the large scale OSS project is not just an individual either, but most likely acting as an employee of a corporation that uses an open source component and needs certain things in it.
There is very limited number of essentially non-commercial licenses. Which makes things hard for this sort of goals. But on other hand some think that such limitations go against open source too...
In my mind there should be no threshold on who should pay for use if they profit. It should not be limited only to mega corporations. You have tens of thousands in revenue, surely you can pay for code you use?
It will still cause financial problems for the user that currently use redis offered by those clous companies as they will 100% increase the prices to cope with the changes and at the same time make more money.
The price of running it on a VM _including_ your real cost of supporting it is the ceiling.
My point is simply that if a licensing change meant that a cloud provider had to pass on extra costs, there is a natural feedback mechanism.
If AWS ElastiCache prices doubled, a lot of people would be doing the math versus whatever they pay for labor. There’s some room to grow there but it’s not infinite.
If you don't want to pay a premium, there are other projects you can support.
This is the same reason Postgres and Redis became extremely popular in the 2010s was because companies didn't want to pay a premium to Oracle or IBM for their DBMSes.
There are other options that exist today as well.
Non-paying or non-contributing users are not entitled to first class support from contributors.
Similarly, contributors and projects are not entitled to users.
According to this comment[1], redis is mostly contributions from other people. I find it pretty outrageous when I contribute code to something if the end goal is to succeed from contributions like mine in taking away the platform I was using and making a monopoly lock in on my preferred solution to my needs like Oracle.
At the top of the software stack it is a horror that everyone bellow you can always choose something else. Stand on your own two feet and achieve nothing or invest knowing your investments may be canceled by politics, monetization, etc.
I.e. if there is too much fragments in redis alternatives, whatever skills or contributions you made you can't use in any organization because they will avoid all redis like solutions.
It is the job of senior Engineering leadership to take these considerations into account.
Some decide to purchase, others decide to build in house, and others yet decide to design in an agnostic manner.
Software is a tool used to build products.
We can nerd out about a hammer all we want, but if you aren't a hammer manufacturer, a major hammer buyer, or someone who has critically contributed to the R&D of the entire hammer industry, your opinions are basically useless.
I personally don't care what hammer is used so long as my house is built.
If this truly irks you, you absolutely should create an alternative.
> I.e. if there is too much fragments in redis alternatives, whatever skills or contributions you made you can't use in any organization because they will avoid all redis like solutions
Patently false, as the proliferation of SQL and SQL-esque systems has shown.
BUT: Amazon, Google and Microsoft (et al) will have to pay if they offer Redis as part of their cloud.
Seems fair and any article not giving a voice to those being reported on is trash. Here you go, though: Under the new license, CLOUD SERVICE PROVIDERS hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge. https://redis.com/blog/redis-adopts-dual-source-available-li...