I do not understand why would a developer (or development team) change the licensing terms of their software for something stricter, like Redis did. Could someone tell me what the factors are?
this post was submitted on 21 Mar 2024
304 points (93.4% liked)
Programming
17416 readers
102 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I guess it's things like AWS Elasticahe that made them want to provide their own service without sharing the code with their soon to be competitors.
Great timing that Microsoft just released a drop-in replacement that's in order of magnitude faster: https://github.com/microsoft/garnet
Written in C# too, so it's incredibly easy to extend and write performant functions for.
It needs to be a bit more deployable though but they only just opened the repo, so I'll wait.
Can it do everything that redis can?
Not everything. There's a list of currently supported and unsupported apis on the docs. Streams aren't supported at all, for example.
The repo description says it works with existing Redis clients, so probably.
load more comments
(1 replies)
What a disingenuous take. Just because the OSI doesn't recognize the SSPL as open source doesn't mean it's not open source.
Edit: Everyone seems to believe I'm saying that because the source is available it should be open source. That's not what I'm saying at all.
Source Available < Open Source < Free Software
These terms have specific definitions, where each greater term is more specific than the lesser*.
SSPL is in the "Source Available" tier.
The OSI defines the term "open source," and the FSF defines the term "free software." The number one term of open source, greater than the availability of the source code, is the freedom to redistribute.
https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses
* Free Software isn't exactly a subset of Open Source. There are a few licenses which are considered Free but not Open: the original BSD license, CC0, OpenSSL, WTFPL, XFree86 1.1, and Zope 1.0.
I don't believe we should let the OSI and FSF be the absolute final say in what people consider to be open source/free software.
The number one term of open source, greater than the availability of the source code, is the freedom to redistribute.
SSPL allows this.
Absolutely. The source of Windows is widely made available to innumerable third parties, yet I've never seen anyone claim that it's open source.
load more comments
(4 replies)
load more comments
(2 replies)