I like how this shows how software being open source ensures the continuous availability of such software, even after the original version is no longer open sourced
I've said it before and I'll say it again; open source's primary purpose is the developer waiving the right to fuck over their users. (Beyond that of a mild inconveniencing) The security, accountability, and crowdsourcing of improvements are all secondary to that.
The interesting part are the Redis modules which already had the new license on them like Search and Json, I'm surprised you didn't cover this topic since it's also a huge selling point for Dragonfly compared to the rest of the clones. Regarding performance, they are all the same, sure, you can say that you handle x amount of ops/s but in the end they are a primary memory key value store that is put in front of network, that will always be their bottleneck
"since it's also a huge selling point for Dragonfly compared to the rest of the clones." Just because dragonfly uses the BSL, doesn't mean its all-of-a-sudden more or less compatible with other BSL licensed software. Actually depending on additional license grants it can be compelely uncompatible with other BSL licensed code. ValKey (BSL, MIT etc) and such are completely compatible however. Although the modules would need to only be used/included in compliance with the BSL
@@kjeldschouten-lebbing6260 Dragonfly has their own implementation of the FT and JSON modules, my apologies if my comment wasn't clear enough that I wasn't talking about the interoperability of their licenses
Very unlikely for snap to switch to valkey. They invested in keydb rather than contributing to redis, there’s zero reason they would suddenly push those changes to valkey. Much more likely that valkey is putting their name on the site because someone from snap messaged the valkey team, rather than snap actually supporting the project.
why would they include the snap icon, just because they call them? do you think the Valkey team would be so disingenuous and Snapchat so desperate to begin with?
I also think its unlikely, they change from KeyDB to Valkey, btw And probably purely because of a simple "not invented here" point of view the Valkey people could theoretically just merge it themselves obviously although i dont even know, if they happen to be interested the license at least is the same
@@shalokshalom I mean, that’s literally how it works. They included the snap icon because snap “supports” the project. Note that the Linux foundation article gives no mention of any of those companies stating intent to use. In fact even the Google person they’re quoting doesn’t state that Google is supporting the project, just that “I am pleased to see the Valkey project come together to continue true open source development. The community's resilience and commitment to the project means we can continue the same innovative work that users have come to admire and depend upon.” Many companies put resources into open source with no intent to use the projects. They’re marketing tools. And Linux foundation can easily state that they’re “supported” because contributors to redis have commented on valkey being a good idea. It’s not disingenuous, but it sure doesn’t indicate any intent on the actions of those companies.
@@kodekorp2064 You can just google Microsoft Garnet and read yourself if you're interested to know. You'll find detail in their Github, much better than my comment.
@@lukealadeen7836 a month or so ago, the White House recommended using memory-safe programming language; which naturally implies that if you’re bidding for a contract and you use it when your competitors don’t, you’re heavily favoured to win
let redis cost money for cloud providers to use. microsoft, amazon and others have been raking in billions for years off the backs of projects like this. one small licensing switch and they're scrambling to abandon ship as fast as possible to avoid paying a licensing fee, it's embarrassing really.
You do know that many large contributors to the project are from said companies right? And not like ones that fix minor issues and refactor things, but people who have worked on major changes and features within redis, so I wouldn't say that they were using it for free, they were quite literally working on said project with everyone else. Plus, the new licensing doesn't just ruin it for the big guys, it also hinders using/contributing to the project for everyone else too. It especially fucks over anyone who had contributed to the project before in the name of open source, just to see the license change, even though Redis had said that they won't change the license. Majority of people that are jumping ship are actually developers, and not the companies themselves, albeit the new projects are sponsored by the big companies.
@@raremc1620 Ikr , definitely feels like a rugpull , the problem was , nobody knew this was coming , no discussions were done , what if they extend this license even further , they have set the precedent. Also SSPL is definitely harsh , I guess companies could've even allowed GPL I suppose
What I find embarrassing is seeing comments like yours. When was your last contribution to an open-source project that you used in a project you sold to a client? And I mean a financial contribution. 99.9% of the 'open source' community just like the free stuff.
I remember when redis launched, oh its better tham Memcached blah blah blah. Im probably one of a few people to never once have used redis, just never bothered with it, plenty of other packages that just work, and whilst redis offers some cool features vs others thats all they are cool features, most of which you can do yourself with a few lines of code. And im still not using redis, i think this a storm in a teacup really do, the only people shouting are the handfull who are affected.
As if anyone wants to use microtrash I mean soft the entire "windows server" itself is a joke as windows was made for personal computers... not servers.
I used to have similar feelings, and still do for the most part, but credit where credit's due: MS SQL server is amazing. vs code came in and rightfully dominated the IDE market. C# is reasonably good, typescript is great, and F# is truly gorgeous. I feel Microsoft builds great developer focused products but absolutely horrendous lambda user / sysadmin products.
@@sheanmassey mssql is dogtrash Select Top 10 * (columns) syntax is so garbage compared to just LIMIT 10 Also lets not even mention no good async db drivers in most programming languages.
@@sheanmassey that's how they pull devs on their side (especially after a time where their reputation was very bad), it doesn't mean there is no ill will
I'm ngl, I was against my old company's move to Microsoft Azure for development. I actually really enjoy the DX using Azure tools / API's and their docs are always pretty on point. If you have notes to improve on their docs, they seem to be consistent with improving it. Their support teams are pretty great if you use it. Their CD/CI is pretty decent too. Honestly I was surprised at how decent their dev platform is.
