461–470 of 815 posts
Earlier quoted context omitted.
> Because fragmentation is apparently good? I think it's more "they are no longer piggybacking off our work for free". I also think what they actually wanted was that plus "...and they paid us".
The reason the ValKey fork happened so fast is that AWS was already sponsoring developers for the open source redis project.
Earlier quoted context omitted.
Not true, you can compete with the quality of the deployed service _separate_ from the development of the software. The quality of the service can include internal, at-scale optimizations that don't affect user-facing parity with the open-source software. Open source companies with SaaS offerings need to have plans to differentiate themselves on hosting quality, not features. Yes, you can do better at hosting your ow…
> Not true, you can compete with the quality of the deployed service _separate_ from the development of the software. That is true in a literal sense but (anecdotally) from the point of view of an engineer deploying ie; Redis, there is no real space for that angle of competition when the choice is between having to go through procurement hurdles to sign a contract with Redis Labs versus say; spinning up Redis on AWS…
And that's not an appeal to authority: there just so genuinely and obviously is no such guarantee in enterprise that quality will ensure success that explaining it feels like trying to break down an elementary element.
After what Mullenweg has pulled, in the era of Blogging CEOs I have to be cynical. Valkey.
Very interesting that this is happening at the same time that NATS is going proprietary. Obviously Redis is way more well known, but as someone who has built a bunch on NATS over the last few years, this makes Redis an interesting choice to migrate to again.
apparently synadia is working with the linux foundation now to find a better way forward, and will release a joint statement soon. (CEO mentioned in their slack)
Literally the day after I started working on moving to Valkey... That's how it goes.
When Antirez left Redis, he wrote an amazing blog post I go back to often [0]. In there he said: "I write code in order to express myself, and I consider what I code an artifact, rather than just something useful to get things done. I would say that what I write is useful just as a side effect, but my first goal is to make something that is, in some way, beautiful. In essence, I would rather be remembered as a bad ar…
I contributed a minor (but imho still neat :p) improvement to Redis under its original license, and personally moved to using redict when the unexpected license change to SSPL was announced - and I was feeling betrayed as a contributor to a properly-FOSS-codebase. (Had they switched to AGPL right away, I'd have been perfectly fine with that change from a moral perspective, ftr.) I have a great deal of respect for ant…
Yeah, we just did this whole ride with Elastic [0]: company changes the license out from under the community, community revolts, company gives up and changes it back. Both companies even pulled the same "it worked" excuse ("while it was painful, it worked", "this achieved our goal"). Neither company has built in a legal safety mechanism to prevent themselves from pulling the rug again later and both companies have sh…
Previous versions are still available under the original license, right? So if you don't want to use it with a new license, you're in the same situation as if company went out of business or stopped support and development for any other reason. There are no safety mechanisms for that either.
I'm curious whether the community will trust Redis-the-company again after this, or if they'll choose to stick with Valkey. The other concern is at least some big company legal departments are wary of AGPL software, which makes Valkey, still BSD, more attractive to them. Edit: Regardless, thank you and the rest of the folks inside Redis for pushing to bring this back to OSS!
Statistically nobody is using valkey.
It was pretty easy, a small config change and some performance testing to make sure it worked well at scale.
Maybe nobody is talking about it online but some people have definitely switched.
Earlier quoted context omitted.
Well that's a reason not to use a distro right? If I type `sudo dnf install redis`, I want to install redis not valkey.
> Well that's a reason not to use a distro right? If I type `sudo dnf install redis`, I want to install redis not valkey. Using a distro that handles things your way is your privilege. I assume most people who install packages care about the functionality they provide, not the brand name - so it seems like a fair default for distros that aim to appeal to broad user bases imo.
Also, what happens if functionality drifts?
Earlier quoted context omitted.
I can easily see this for a midsize company. While it's likely an easy process to drop in valkey, creating the new instances, migrating apps to those new instances, and making sure there's not some hidden regression (even though it's "drop in") all takes time. At a minimum, 1 or 2 hours per app optimistically. My company has hundreds of apps (hurray microservices). That's where "hundreds of hours" seems pretty reason…
> My company has hundreds of apps (hurray microservices). That's where "hundreds of hours" seems pretty reasonable to me. Sounds like a huge disadvantage in your company’s choice of software architecture to me.
Sometimes large companies acquire smaller companies and keep the lights on in the old system for a while. They may not even use a similar tech stack!
Sometimes they want to cleanly incorporate the acquired systems into the existing architecture but that might take years of development time.
Sometimes having a distributed system can be beneficial. Pros / cons.
and sometimes it’s just a big company with many people working in parallel, where it’s hard to deploy everything as a single web app in a single pipeline.