News for hackers. Stuff that matters.
Re:Redis Adopts Dual Source-Available Licensing by lamontcg on Thursday March 21, 2024 @01:08PM (#39781364)
> Most Redis users have never paid the company behind it even a single cent. Me included. So, I can appreciate them doing this in order to make some money. Except it won't change my behavior; I'll just use the fork.

Do you not see how incredibly entitled this is?

If everyone does this then there's no money to maintain the fork, and you're looking for slaves to run it. Or else everything FOSS just gets maintained by employees at massive tech companies that have other businesses which fund it.

Re:Redis Adopts Dual Source-Available Licensing by smokel on Thursday March 21, 2024 @02:14PM (#39782285)
It is, however, also incredibly realistic.

People are not using open source for the hippie philosophy. They are using it because it is free (as in beer), but even more importantly: they are using it because non-free licenses are a terrible pain in the ass.

Legal aspects are a headache, and the amount of effort to get someone in your company to pay even a tiny amount for some library or service is a serious hurdle.

I would not be surprised if adopting a non-free library would take a typical company ~40 man hours of work. At current rates, that translates to quite an expensive license.

Re:Redis Adopts Dual Source-Available Licensing by bluGill on Thursday March 21, 2024 @02:51PM (#39782799)
Just getting open source adopted in my company takes around 10 man hours, and that is for something like a compiler that is only for internal use. If we will ship/expose it to customers we do due dalliance that probably amounts to 40+ man-hours to verify we can accept the license terms for that use and that the project doesn't have some hidden license issue (someone copied in code with a different license, link to something with a different license...).

Getting close source is even more work though - now we need someone to negotiate license terms (that is make sure our proposed use is compatible with the license we buy). We also make sure there is no risk of using their code (what if the closed source binary library has some AGPL3 code in it). I'm not even sure how to go through that process.

Re:Redis Adopts Dual Source-Available Licensing by api on Thursday March 21, 2024 @04:48PM (#39784221)
That may be true, but a lot of the creators of open source do in fact do it for the "hippie philosophy." That disconnect will eventually kill it. Why work hard to just be free labor for SaaS companies and people who don't care about you?
Re:Redis Adopts Dual Source-Available Licensing by salmo on Thursday March 21, 2024 @09:45PM (#39786633)
The problem I’ve seen historically is when a company is founded around one project or ecosystem.

Someone like Microsoft or Google could take software like this, pay the original developer, and still see tons of ROI offering it as a canned cloud service. And to a certain degree they don’t care about the profitability of that 1 thing if it helps sell the rest of their system. Quite honestly, they won’t care about competition using it if it’s already common. People want X, they’re using it, you can offer it. You’re paying a handful of people for street cred, a guarantee it will continue to work well with your stuff, and input into direction.

Folks like RedisLabs, MongoDB, Hashicorp, etc. think they can do the same with a marketplace offering. But they’re reliant that the particular product is profitable on its own. They’re also reliant on the cloud customer being willing to establish another relationship with another vendor, even when they can automatically deploy and bill through their existing provider.

We’ve seen folks behind OSS projects hop from company to company over time and the project continues to thrive. I haven’t seen a company restrict a license and the project do so… at least that I can think of. I might be wrong.

Re:Redis Adopts Dual Source-Available Licensing by indymike on Thursday March 21, 2024 @02:33PM (#39782564)
> Do you not see how incredibly entitled this is?

No. I think part of the value of Redis to date was exactly that it was BSD licensed. When I started using it, I showed many other developers what they could do with it, and those devs took Redis to work, and built products and some bought services/products from Redis. Without the open source product, Redis the company would likely not exist as it does today. Times change, and the right strategy for Redis the company probably looks a lot different than when they started it on the back of Antirez's still awesome software.

Re:Redis Adopts Dual Source-Available Licensing by api on Thursday March 21, 2024 @02:12PM (#39782259)
This is the issue: FOSS has largely become free labor for SaaS companies.
Re:Redis Adopts Dual Source-Available Licensing by baggy_trough on Thursday March 21, 2024 @02:21PM (#39782390)
Your use of "slaves" is a remarkably offensive way to describe volunteer software developers.
Re:Redis Adopts Dual Source-Available Licensing by lamontcg on Sunday March 31, 2024 @11:51AM (#39885332)
After reading about the situation that Lasse Collin was in with xz before their mental health problems were exploited by a likely state actor I'm 100% not fucking apologizing for using that word to describe how unpaid maintainers of critical open source software are being treated. It is more or less fucking appalling and if I have to use shocking language to get the point across I absolutely fucking will. And I'm tired as fuck of how we can't use any strong language to talk about situations that demand strong language because some theoretical person might take offense to it. This is fucking bullshit and needs to change, and we need fewer language gatekeeping assholes who aren't making anything better. So sick of this shit.