Live data from Hacker News

From where I left

antirez.com

101–110 of 472 posts

Re: From where I left

#101
post #82
post #68

For me, the license change upset me mainly for two reasons: 1. Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc - and when they did that it was under the understanding that project would remain under the same open source license. It honestly felt like a betrayal of trust. 2. From a purely selfish point…

"Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc" I can understand that, but the thing about the BSD license is that such value never gets lost. People are able to fork, and after a fork for the original project to still lead will be require to put something more on the table. Inside Redis it was tried…

I'm embarrassed to admit that I hadn't fully taken into account that those contributions do at least remain under the BSD license and hence stay open under those original terms. Thanks for reminding me of that.

Re: From where I left

#103
post #71

> 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,…

Please keep writing, I want to read your fiction. I cal tell you have style from your blog entries. Lean into the style and readers will love you for it.

Re: From where I left

#104

Earlier quoted context omitted.

fork of redis https://github.com/valkey-io/valkey just before the transition to their new source available licenses

Ah thanks. Is this by AWS or similar?

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.

Re: From where I left

#105
post #98

Earlier quoted context omitted.

What’s valkey?

It's the Redis fork with the most resources and the most backing. It's well funded and it sits under the Linux foundation: https://www.linuxfoundation.org/press/linux-foundation-launc...

and remains truly open-source, unlike Redis.

Re: From where I left

#106
post #84

Earlier quoted context omitted.

The question of what constitutes a "service" seems very murky, and although it's obviously not the intention of all these source-available, BSL style things, in a dark timeline it seems like there's a lot of room for litigious actors to behave very badly. The uncertainty is what makes it scary, I'd also like a lot more clarity.

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).

the issues of sspl have been frequently and loudly been brought up previously, and nothing has happened. just to reiterate, this section is ridiculously expansive:

> “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.

it is practically impossible for anyone to comply with that, to provide source code for every single program (without limitation) that they happen to use anywhere. of course none of the major sspl-using vendors are even pretending to themselves to follow these rules.

sspl would be much better license if it just simply forbids providing services, instead of hiding behind this thin veneer of fake copyleft.

> You can even still sell Redis as a service if you want, as long as you release all the orchestration systems under the same license (something that nobody would likely do, but this shows the copyleft approach of the license).

note that this is not right, the "copyleft" is not limited to orchestration systems, it covers all programs that you use

Re: From where I left

#107
> 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)

I wrote and published my first book in a weekend frenzy and it’s one of my favorite accomplishments.

I’ve published half a dozen small books since then, the most popular of which is about how to write and publish your own book.

Over the past couple months I’ve been preparing a system to help others publish their own book. If you have any interest in writing and publishing, please reach out. I’d love to help.

Re: From where I left

#108
post #93

Earlier quoted context omitted.

In a sense valkey is the main line and redis is now the fork. Valkey is about the same except losing the trademark. It’s similar to Hudson and Jenkins. It’s not so clear cut with OpenSearch.

IMHO the "real" Redis is not about licensing, but about design (as long as the license is acceptable, as I think it is in both cases). We will see.

That’s a nice way of looking at it. It’s quite an influential project. I’m just now thinking of taking more direct inspiration from it for a micro-library for webassembly.

I wish you success in Redis Labs and thanks for Redis. In my other comment I said I never considered using Redis under the new license, but I didn’t say that I never would consider it, and I think I would if I found myself on a project that needs a key value database with enterprise support or more bells and whistles. I think it has its place, and to me it is an awful lot like postgres and EnterpriseDB, especially if Redis Labs gives its blessing, directly or tacitly, to adding this new vector type to valkey.

Re: From where I left

#109

I'm really interested in this bit: "the fracture with the community is not about licensing, or at least it’s not mainly about licensing" I wish he'd elaborated a bit more on what he thought it was about. My understanding is that it's 100% about the license. That's certainly why I'll reach for valkey instead of redis next time I need it. That's also what I've heard from everyone else in a similar position. What else w…

For somebody, like you and many others, it was very important to retain an OSI license. But I feel that in general given that the new license is IMHO good for almost every user, from the POV of what they can do with the code, and that the cloud situation was quite self evident, I believe that with better communication, and immediate developments/merges in the core, to counter balance the license switch, many people would understand the license matter.

We will not win back you as a user, and I respect that. But many, many users that see openness, good features and documentation, the github repository at the center of everything: I believe they will appreciate this, and can decide that Redis is good for them.

Re: From where I left

#110
post #22

Earlier quoted context omitted.

TLDR API: VADD key [VALUES | FP32 ] element VSIM key [VALUES ... | FP32 ... | ELE ...] [COUNT ] [EPSION ] VCARD key (number of elements) VDIM key (dimension of the vectors) VDEL key And so forth. However there are nice things you can enable, if you want. For instance VADD has the [REDUCE] option that implements random projection in order to reduce the dimensionality of your embeddings. Less memory, and it is faster.…

yes loving this! please PLEASE be the hero we need in unfucking the unholy mess of misdirection and useless abstraction that is storing some vectors somewhere for similarity search right now

U mean there are too much leaky abstractions in the field now ?
Post reply on HN