Isn't this a little old?
Redis is forked
121–130 of 206 posts
Re: Redis is forked
#122Earlier quoted context omitted.
With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. OSI Open-source business models…
> But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. According to antirez, he understood the implications of licensing Redis as BSD: https://news.ycombinator.com/item?id=39863371
But not in "the era of big tech cloud computing":
> That is, if I was still in charge, would I change license? But that's an impossible game to play, I'm away from the company for four years and I'm not facing the current issues with AWS impossible-to-compete-with scenario.
Not saying he would have decided any differently, just that cloud computing has changed open source situation for the worse.
Re: Redis is forked
#123Microsoft Garnet is the only redis fork that actually improves upon it, improving performance by an order of magnitude. Maybe the others will catch up, but it's very "Hacker News-esque" to fail to mention something the largest company in the world is working on.
As far as I know, Garnet is not a Redis fork, but a new software that happens to implement the Redis protocol to be compatible with its clients.
Re: Redis is forked
#124Changing from an open source license is a kind of tech product spin on enshitification. Even if the product continues to get features and active development, like Oracle poured into MySQL after its acquisition, a database or framework going less open source is still a death knell. The mainstream programmers will move on and use something else. Anything else. Who who has heard that the license can change would now pic…
I'm confused. Does SSPL not require more sharing of source code than GPL and the like? I've always thought the "we're just hosting a server with our modified version of this OSS code, so we don't have to share the source" argument was trash.
It's not even being compared to GPL. The original licence was BSD. You're right, these licences are meant to make things more free. It's incredible to me that even software engineers can't see beyond local optima and convenience to the bigger picture. BSD is like saying "you're free to do anything including throwing shit over your neighbour's fence". Individual freedom is basically irrelevant. It's community freedom that matters.
Re: Redis is forked
#125Earlier quoted context omitted.
With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. OSI Open-source business models…
> Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. Well, know what your secret sauce is. I think performance is really the best differentiator. Make a fully behaviourally compatible (maybe not bug for bug) version available and then sell a proprietary faster version. Think an compiler that doesn't due any optimisation and outputs naive code. You know have a useful OSI proje…
>I think performance is really the best differentiator.
I don't understand this at all. Most open source projects start out equally as a means to give back to and collaborate with the community as well as showcase one's skills. You're asking me to purposefully publish badly optimized software? I don't have it in me. That offends my sensibilities of craftsmanship. A 'slow' open source project will never get traction. Even if it did, I also don't know how an open source project wouldn't immediately have it's obvious performance bottlenecks fixed.
Far better to go the VSCode route. Release a useful project, then release paid extensions for it.
Re: Redis is forked
#126Microsoft Garnet is the only redis fork that actually improves upon it, improving performance by an order of magnitude. Maybe the others will catch up, but it's very "Hacker News-esque" to fail to mention something the largest company in the world is working on.
[deleted]
Re: Redis is forked
#127Microsoft Garnet is the only redis fork that actually improves upon it, improving performance by an order of magnitude. Maybe the others will catch up, but it's very "Hacker News-esque" to fail to mention something the largest company in the world is working on.
Besides that Garnet is not a fork, as sibling comment mentions, it was recently discussed in HN: https://news.ycombinator.com/item?id=39752504
Re: Redis is forked
#128Can someone ELI5 why I should feel bad about Redis charging massive companies like AWS and Google to use/sell/profit from their software? Am I really supposed to feel like Amazon is the good guy in this situation? As far as I can tell this change doesn't affect 99.999% of Redis users, but I understand I could be missing something?
Re: Redis is forked
#129Can someone ELI5 why I should feel bad about Redis charging massive companies like AWS and Google to use/sell/profit from their software? Am I really supposed to feel like Amazon is the good guy in this situation? As far as I can tell this change doesn't affect 99.999% of Redis users, but I understand I could be missing something?
For a lot of people, myself included, it’s ideological. It’s not about “feeling bad” for gigantic corporations, it’s about what FLOSS stands for. Something either is or isn’t free software, and for a lot of people that doesn’t matter, but it matters to me.
Re: Redis is forked
#130Earlier quoted context omitted.
> The thing that makes the difference is what is running on people's laptops, because that's what people will eventually put into prod. "It works on my machine!" "Then we'll ship your machine" Docker: https://miro.medium.com/v2/resize:fit:720/format:webp/1*Ibnw...
Lol plain old VMs have been shipping your machine since well before Docker was around.
And in some cases, unfortunate git commands will ship your machine too!