Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From where I left

antirez.com

Post reply on HN
Print view View original

91–100 of 472 posts

Re: From where I left

#91

Post by sroussey »

benatkin wrote: post #87
antirez wrote: post #82

Earlier quoted context omitted.

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

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.

What’s valkey?

Re: From where I left

#92

Post by some1else »

simonw wrote: post #74

That vector sets design outlined towards the end of the article is delightful - it's exactly the kind of API design I appreciate from Redis over the years: simple, elegant and feels obviously correct to me.

Where would a Redis vector store play a part though? Maybe you'd load up relevant embeddings for a particular user while they're interacting with their dataset, to make their responses quicker? You've already spent the effort on hydrating their data out of persistence though. I guess step one is likely being a more trusted alternative to the in-memory vector solutions like HNSW, Faiss, and a potentially faster engine than pg_vector. I've always seen Redis as an augmentation, but maybe in this role it can take the helm?

Re: From where I left

#93

Post by antirez »

benatkin wrote: post #87
antirez wrote: post #82

Earlier quoted context omitted.

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

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.

Re: From where I left

#94

Post by alex-moon »

Honestly working as a back-end Web dev is kind of a dream job just because you have these stack apps that are super fast, super stable and do exactly what they say they do. Nginx and PostgreSQL are typical examples, and I consider Redis one as well.

Re: From where I left

#95

Post by benatkin »

sroussey wrote: post #91
benatkin wrote: post #87

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.

What’s valkey?

Persistent key-value database with network interface https://packages.debian.org/testing/database/valkey-server

Re: From where I left

#96

Post by simonw »

some1else wrote: post #92
simonw wrote: post #74

That vector sets design outlined towards the end of the article is delightful - it's exactly the kind of API design I appreciate from Redis over the years: simple, elegant and feels obviously correct to me.

Where would a Redis vector store play a part though? Maybe you'd load up relevant embeddings for a particular user while they're interacting with their dataset, to make their responses quicker? You've already spent the effort on hydrating their data out of persistence though. I guess step one is likely being a more trusted alternative to the in-memory vector solutions like HNSW, Faiss, and a potentially faster engine…

It's exactly that. Redis is an in-memory data structure server that you can outsource index-style operations to. Vector similarity is a type of index search. I think it's an exact fit for Redis.

Re: From where I left

#97

Post by alanwreath »

sroussey wrote: post #91
benatkin wrote: post #87

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.

What’s valkey?

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

Re: From where I left

#98

Post by simonw »

sroussey wrote: post #91
benatkin wrote: post #87

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.

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

Re: From where I left

#100

Post by block_dagger »

munificent wrote: post #64

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

I have had the same experience. With coding I can be in that coveted state of flow for 10 hours straight. With creative writing, I feel exhausted after 3 or 4 hours. I didn’t expect this and don’t fully understand why.
Post reply on HN