Welcome back!
And good timing... our brute force cosine similarity scan on Redis-stored vectors needs some help at the core level (ANN, nearest neighbor, k-mean clustering, anything would be an improvement!)
From where I left
191–200 of 472 posts
Re: From where I left
#192Earlier quoted context omitted.
> Open source is a gift economy. Receiving a gift does not form a social contract that entitles you to future gifts I think op was talking about contributors, who essentially gifted back. One might take offense if they were exchanging gifts with someone, and they open a pop-up store and sell what was gifted. Also, it's also a tiny bit hypocritical to expect revenue sharing with Amazon without doing the same for contr…
Redis has a CLA so contributors can't use their gifts as leverage to control others. https://redis.io/legal/redis-software-grant-and-contributor-...
I don't think you should conflate CONTROL with resentment or distaste or feeling betrayed or feeling misled. They aren't the same.
Re: From where I left
#193Earlier quoted context omitted.
Note though, the code is not Music, it rots quickly without maintenance. The "social contract" of contributing the code is what it will be maintained by collective community, otherwise many companies would just keep it as private forks. It is wonderful thing though, with Open Source, people can band together and "pull Valkey" to create well maintained fork based on all those past contributions
That may be true of node.js codebases, but last time I checked Redis was written in C and only depends on ISO and POSIX standardized stuff. I doubt there's been any leftpads that have broken the old versions by now.
It is not just compatibility, there are bugs, but most important security issues which are constantly being discovered.
Re: From where I left
#194Earlier quoted context omitted.
Redis has a CLA so contributors can't use their gifts as leverage to control others. https://redis.io/legal/redis-software-grant-and-contributor-...
I don't think you should conflate CONTROL with resentment or distaste or feeling betrayed or feeling misled. They aren't the same.
Even without a CLA, Redis was originally licensed BSD. Releasing code under a BSD license is making a promise that you are OK with people using your code for commercial purposes. If you as a developer express personal feelings of dissatisfaction that someone is doing with your gift what you gave them permission to do, in such a way that could be construed as reneging on your promise, then that would make you dishonorable and untrustworthy.
Re: From where I left
#195Earlier quoted context omitted.
It is really hard to believe that no one defends antirez&co as protecting themselves from greedy overpriced SaaS businesses who were parasiting others hard work. What about them saases breaking a social contract of giving reasonable prices adequate to the effort put into a product (or a wrapper around the product)?
Yeah, this is weird. The one restriction is one you probably dont care about because you're not amazon or azure yet some people still freak out like youve taken their toys away. Truly odd.
It's not that weird. With a FOSS license, I know I can use a program for anything I choose to and the terms will never change. I might launch a startup with a friend tomorrow using a package and complying with its license terms, and a million dollars later we're still legally entitled to use it.
Adding constraints later is a non-fallacious slippery slope. The restrictions Redis added aren't directly onerous to 99.999% of users, but now the world is divided into people who are allowed to use it at will, and people who can only use it in certain ways (or not at all). That's an enormous change from a FOSS license. And if they change it today specifically to lock out Amazon, will they change it again tomorrow to lock out my startup? The thing is, now that they've established precedent, there's no way of knowing what'll happen later.
Again, I know I can use GPL or MIT or BSD software for anything I want as long as I play by the exact same rules as everyone else. There's nothing that says you can use it but I can't. The difference between Free to non-Free is vast, even when I'm not affected (yet).
Re: From where I left
#196Earlier quoted context omitted.
I'm sorry, but how is this a good answer? If you really only care about "two/three users in the world" and don't want users to worry about legal implications, why not explicitly write that in the license? It doesn't matter how good your intentions are, in the long run, it's not you or Redis, inc. we have to trust, it's anyone who potentially inherits the rights of these licensed IPs, at which point the courts will no…
A cynical view is that it's not just 2-3 providers, its any competition to their cloud-hosting business. See for example the recent wordpress drama, which concerns a small competitor. SSPL and related licenses are ambiguous and scary enough to ward off anyone potentially competing with the copyright owner, and I doubt that's seen as a downside.
This is a really good example of why software with a license that is basically "this could hurt you but, like, trust me bro" isn't worth building with/extending/learning. It feels a LOT like a landmine waiting to detonate.
Even if I'm doing completely non commercial work I never ever ever will want to productize in any way I'd rather build my skills and familiarity with something portable (and I don't want to have to remember when I can and can't safely use each part of my stack). Anything else is just asking for a future nightmare.
The oracle and wordpress stuff recently are devastating. Can you imagine having to grind your entire company to a halt looking for anything that uses anything that uses anything that uses redis/java/whatever?
I'm an engineer. I can't justify a fixed amount of upside for an unbounded downside if I ever get on some stranger's bad side for whatever reason.
Re: From where I left
#197> However, during the “writing years” (I’m still writing, by the way), I often returned to coding, as a way to take breaks from intense writing sessions (writing is the only mental activity I found to be a great deal more taxing than coding) This has been my experience too. With both "Game Programming Patterns" and "Crafting Interpreters", writing the code was a joy while writing the prose was hard work. Gratifying,…
Totally agree. It's very hard, especially since when writing fiction, and the kind of fiction I wanted to write, there are a lot of things you doubt about yourself: is my style as good as I wish? Are my stories and my characters strong enough, with the right motivations? And I bet many of this ingredients are still there even when writing technical books if the goal is to do a very good job. Teaching in written form,…
I find, even in the short stories I write, that managing the story arc is so much harder than managing code execution…
Re: From where I left
#198Earlier quoted context omitted.
Yes: https://www.linuxfoundation.org/press/linux-foundation-launc... > Industry participants, including Amazon Web Services (AWS), Google Cloud, Oracle, Ericsson, and Snap Inc. are supporting Valkey.
Cloud providers offer productized versions of Redis, so their interest in Valkey should be obvious :)
Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying.
Re: From where I left
#199Earlier quoted context omitted.
The good thing about this is that since the companies are copyright holder of the code, if this creates issues, the licenses can be rewritten and modified in order to be as sharp as possible in the use cases they want to avoid (which is... two/three users in the world :D).
For the companies who "are copyright holders of the code" the uncertainty and litigation potential is not a bug, it's a feature.
This feature could actually be the overwhelming value of acquiring the copyright. When trillion dollar companies go to war with each other this kind of thing is a fantastic weapon in the arsenal.
Re: From where I left
#200Earlier quoted context omitted.
> I do also see these kinds of license trends as harmful to open source generally I've re-read this a few times and I'm still not sure what "harmful to open source" means in this sentence, could you expand on this a bit when you have time? (readings I considered: this will dissuade people from using OSI licenses, this will dissuade people from trying to monetize open source components, this will dissuade people from…
In this matter, that pretty phrase “social contract” is at root a demand for ego massage from a) contributors that don’t actually believe in the freewheeling spirit of the BSD/MIT licenses but used it anyway, and b) noncontributors whose sense of entitlement is projecting as loss aversion. The revised license is nevertheless a problem for component selection. Usage caveats are a landmine and thereby a coherent motiva…
"A demand for ego massage" is a pretty rude way to try to dismiss away someone's expressed feeling about something they cared about fundamentally changing.
I think it's a stretch to attack everyone who liked the idea of a totally open license as either disingenuous or selfish.