AWS also forked ElasticSearch into their “OpenSearch” DBaaS. It caused some issues at my last job because OpenSearch limited us to a particular version of the NEST .NET library that was missing some newer functionality. Real bummer and feels like a step in the wrong direction given all we’ve accomplished in tech over the last 20 years.
OpenSearch infuriates me to no end. It lacks so many improvements and advancements since the ancient version it was forked at, but because AWS already has an org's payments details, teams often refuse to look at Elasticsearch. Even basic things like autocompleting queries have been WIP for half a decade now: https://github.com/opendistro-for-elasticsearch/sample-code/... https://github.com/opensearch-project/OpenSear…
The race to replace Redis
251–260 of 520 posts
Re: The race to replace Redis
#252Earlier quoted context omitted.
I believe that Redis has an agreement of sorts with Salvatore Sanfilippo / Antirez, the creator of Redis.
Amazon / Google / Microsoft made a massive mistake by not hiring Antirez, it's chump change for them to throw him $1-2M a year at him so he can work on Redis for them full time.
Plus some great projects don’t even get (monetary) contributions from large corporations. I think because it could weaken their legal position.
Re: The race to replace Redis
#253All this outcry about license switch coming from "community" feels funny. After all, if there is the "community" then they can take the last open-source version and keep developing it themselves, right? But most "communities" are about "take, take, take", not "work, work, work". They often upset only because someone declared they aren't going to work for free any more.
Re: The race to replace Redis
#254Earlier quoted context omitted.
Amazon / Google / Microsoft made a massive mistake by not hiring Antirez, it's chump change for them to throw him $1-2M a year at him so he can work on Redis for them full time.
Has anyone asked Filippo if he still wants to work on Redis "for them" though? The fact that he stepped down suggests he doesn't.
Again, it's chump change, these companies drop that kinda money all the time in aquihires..
Re: The race to replace Redis
#255Earlier quoted context omitted.
Isn't that what redict is?
I see that it is. So then I don't see what the hoopla is about at all. The software is all there. Some dickheads forked a proprietary version. They got the name, which will be their consolation prize in their voyage to irrelevance; nice knowing you. Meanwhile, what everyone uses marches on.
Re: The race to replace Redis
#256Earlier quoted context omitted.
> AWS won't be allowed to leech off anymore. Doesn't AWS employ Madelyn Olson? I mean, AWS have paid for Redis development. Not exactly a leech.
Yes, they paid. And they can use the code they paid for. But it doesn't give them right to leech of any future code written by someone else IN THE FUTURE.
It's lose/lose!
Re: The race to replace Redis
#257Earlier quoted context omitted.
Maybe we instead need a model where FOSS is not about profits for anybody, and is just a passion of love, from a large community of amateurs doing it for the technology and fun. Projects could still be funded by community users, but "venture funding"? That's how projects turn to shit.
In such a world most of the open source software you’re used to wouldn’t exist (or would be much less complete) and you’d be forced to work with and use proprietary systems most of the time.
As part of that world, I also want livable wages and work-life balance for developers, so they can work on their passion FOSS off-call. And for students and programming enthusiasts to be more passionate about FOSS. Like in the 90s before the corporates took over FOSS.
If some FOSS still wouldn't exist then, I'm fine with that.
Re: The race to replace Redis
#258Earlier quoted context omitted.
> AWS won't be allowed to leech off anymore. Doesn't AWS employ Madelyn Olson? I mean, AWS have paid for Redis development. Not exactly a leech.
Yep still the biggest leachers. Token hires and flowery PR campaigns doesn't entitle them to most of the profits of other vendors products or absolve them of their predatory behavior. But they wont be able to leech Redis's future contributions. Knowing AWS they'll most likely create a fork to continue raking in most of the profits in the short-term.
> Yep still the biggest leachers
Redis was literally licensed for people to do whatever they want. That's not leeching.
Re: The race to replace Redis
#259Earlier quoted context omitted.
> AWS won't be allowed to leech off anymore. Doesn't AWS employ Madelyn Olson? I mean, AWS have paid for Redis development. Not exactly a leech.
Yes, they paid. And they can use the code they paid for. But it doesn't give them right to leech of any future code written by someone else IN THE FUTURE.
Code contributions from amazon would've been leeched by other parties using redis as well - something which amazon is accepting (and probably encouraging).
Re: The race to replace Redis
#260Redis, Redis, again more about Redis .... From you people who know a lot about Redis, help me out here: For my Web site code (for my startup), I needed a key-value store. Soooo, it looks like I could use Redis for that. But instead, wrote a little code using two instances of a Microsoft .NET collection class . Simple code. Plenty fast. Welcome programming exercise using .NET classes. Cheap -- no ongoing charges and n…
https://learn.microsoft.com/en-us/dotnet/standard/collection...