261–270 of 520 posts
Earlier quoted context omitted.
Not only that, AWS has been offering redis-as-a-service longer than the "Redis" organization has been.
But if the shoe were on the other foot, AWS wouldn’t hesitate to rip the carpet from under anyone.
Earlier quoted context omitted.
The vast majority. Only 7.7% is unpaid: https://thenewstack.io/contributes-linux-kernel/
Which is not inherently surprising. Developers need a salary to pay the bills. Let's say that covers the first 40 hours of the week. Those who are searching for significance outside their day job offer free labor as their "hobby". Maybe 10 hours a week? For projects that want to move forward with some velocity it makes sense to make some of that development into paid day-jobs. As projects get very large, there's a fa…
>This is the cognitive dissonance that underpins OSS development. The very people OSS treat as the "enemy" are the people funding OSS in the first place. As much as say RMS rails against big tech, Linux and the rich Linux economy system only exist at the level they do -because- of big tech
Perhaps that's the problem: that they exist "at the level they do", meaning most of it is corporate focused, and not enthusiast and user focused.
Even ourselves, as devs, evaluate FOSS as to whether it's "useful" for our corporate/startup needs. This wasn't exactly the case, or at least not the main case for a FOSS project.
Gnome, for example, wasn't created to give RH and co a desktop shell for corporate installs...
Earlier quoted context omitted.
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…
Opensearch has been great so far, no issues ever since deploying the very initial forked version. Neither of those links seem like dealbreakers, am I missing something? Is the idea that opensearch is not usable in production because of missing autocomplete?
> Is the idea that opensearch is not usable in production
No one said it's not usable in production.
> because of missing autocomplete?
We have an operations team that wants to do searches across 200+ fields for an embedded device's logs. The engine supports it just fine, but what kind of UX is it to expect them to do manual lookups of the fields available?
People with simple use cases of course can't imagine how important discovery features are.
Of course those aren't all the parity gaps, a random sampling of the ones I banged my head against:
- No Log Stream view, also critical for observability operations with any semblance of a reasonable UX
- No wildcard type, critical for machine generated logs having sane searchability. Searches are literally broken otherwise by false negatives.
- No nested fields in visualizations, can't visualize properly structured logs.
- Can't change indexes on visualizations, need to recreate the entire visualization.
- Can't use underscores at the start of a field name.
- Doesn't support auto refreshing fields which again, is terrible for embedding device logging
Elastic moved past basic search since the days OS forked it at, and now it's a genuinely nice choice for observability.
There's a literal report I wrote on the gaps there to justify going to Elastic before giving up on our slow RFP process. Every gap no matter how small is representative of what's wrong with OpenSearch: they don't have 1/10th the incentive to actually put comparable resources to Elastic behind it.
Especially when you have people lining up to make excuses based on the fact they're clueless about the gaps between them. Literal droves of people using it to provide a middling search experience to their users just don't see anything wrong with it.
All 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.
In this case the community is the biggest contributor to Redis. The ones that "take, take, take" is Redis the company. Your comment seems way out of place in this light.
Isn't this the reason why AGPL has started to get more popular? Everyone has to play by the very strict rules except the copyright holder, who can do whatever they want, but the community still benefits from the core software being open source. The BSD license in particular seems like a particularly bad way to run a business.
The whole move to new "open-core" licenses started with the most famous (infamous?) AGPL project - MongoDB. The AGPL is not what companies like this want (Mongo, Elastic, Redis etc). They don't want AWS's code: AWS is already providing that. They want AWS to pay them royalties or stop competing.
but at the same time, they want people to be able to use the software for free (esp. at the start), to kick-start the network effect.
In other words, open-core business models want to have their cake and eat it. If you are able to make lots of money off said software, we want a piece of it after the fact. But we dont want to take on the risk of actually looking to build a business and compete on the same.
Earlier quoted context omitted.
If AGPL blocks adoption then "large orgs" can buy commercial license (assuming software is dual-licensed).
They can, but the issue is how much effort does that require for a random dev in the org to go through to try out a project? It's not a technical blocker, it's a psychological blocker
Why don’t we try to fix the “cannot be used for bezos yacht”-licenses instead of shunning the numerous companies of especially databases who want to do good in a meaningful way? Source available is good, better than proprietary which is what we get with aws, but still not enough. People are legitimately afraid of rug pulls, like sneaking in essential features into paid offerings. I think a lot of the skepticism comes…
The "major platform hijacks our code for the web" is a valid concern, but the FOSS people have always kinda gone "well fuck you for having these concerns". That's... I guess fine enough when the majority of FOSS wasn't part of a SaaS stack, but now that the majority of big name libraries and tools are, it's becoming clearer and clearer that the OSD is just too lacking for those concerns.
To be clear, this isn't a defense of SSPL or similar anti-Bezos licenses (the best one I've seen is the BSL, which transforms into a traditional OSS license after X years if you want my opinion), moreso an observation that there's a clear need here that can't be met by OSD. Paying developers on top of the FOSS model is hard; doing support favors entrenched suppliers because of the CYA problem (this is why AWS has the advantage they do) and I'm pretty sure that even if you do the support model, it usually just doesn't pan out.
The main reason 90% of these licenses suck is far moreso because lawyers will draft contracts and licenses in such a way for you that they'll always give you the advantage. The SSPL being borderline impossible to comply with is by design for example.
Microsoft's Garnet has the best chance of replacing Redis, the OSS project and the hosting company. Article doesn't mention it, but supposedly Microsoft uses novel algorithms and multi threading to achieve an order of magnitude improvement in throughput. Now if they can commercialize it with Azure, it should be a credible alternative to Redis Enterprise hosting.
Earlier quoted context omitted.
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.
Err, after this license change Redis Inc will be the biggest leechers considering they didn't contribute the majority of the code. > Yep still the biggest leachers Redis was literally licensed for people to do whatever they want. That's not leeching.
So whilst their previous license allowed AWS to leech off them, it's now been relicensed to prevent them from profiting off their future investments without compensating anything back.