Live data from Hacker News

From where I left

antirez.com

81–90 of 472 posts

Re: From where I left

#81
> The license language is almost the same as the AGPL, with changes regarding the SAAS stuff. So, not OSI approved? Yes, but I have issues calling the SSPL a closed license.

The AGPL is a nonfree license, despite being erroneously classified as a free one. It is a nonsensical EULA masquerading as a copyright license, and I’m not the only person to point this out.

Comparing your nonfree license to the AGPL might seem like an argument in favor of the open-ness of your license, but in reality it is a condemnation.

It is insane to think that you should be able to dictate what happens to software that other people run on their own computers that you have given away as free software.

The AGPL and SSPL both demand this, for different reasons. Both are nonfree and both are wrong.

Re: From where I left

#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 very hard to don't change license. For years it was some kind of "dogma", something one could not even speak about. Then after all the kind of attempts, and following the experiences of MongoDB and others, finally this choice was made. (Disclaimer: I saw the switch as an outsider, so my information is not complete about the final decisions -- I for sure know how this was always considered to avoid if other setups were possible).

However now I see that there is the case for giving the community something in exchange to the license change: a lot of good things in the core, a very good attitude towards the community, and so forth.

Re: From where I left

#83
post #22
post #17

Earlier quoted context omitted.

Well, the VSIM example I got inside of 10 seconds, so at least for now you're on track :)

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

Re: From where I left

#84
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…

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

Re: From where I left

#85
I've never had a use for Redis, but I was very happy to read this, and sincerely wish him the very best of luck. He seems to have his priorities straight.

I am 62, and write more software, now, than I ever did. This time, though, it's for free. I make it a point to treat my projects as "top-shelf" professional-grade shipping software, as opposed to the "hobby-grade" that I see from many folks I know that write non-commercial software.

That's just me, and the way I do things. WFM. YMMV.

Anyway, hats off to him, and the best of luck!

Re: From where I left

#86
post #63
post #7

[flagged]

If you don't like the productivity boost AI gives programmers, how do you feel about the productivity boost that open source gives programmers? I would argue that the open source community is responsible for WAY more of a free/cheap productivity boost for programmers than generative AI, and we've been providing that productivity boost for decades.

I think these are two different issues:

Open source mostly enhances devops productivity. AI directly plagiarizes. I do not see anything wrong with not having to write your own shell, but regurgitating laundered code and algorithms is wrong and should be illegal.

With AI the original authors do not even get credit, with open source they do.

If a human plagiarizes open source directly, it is also wrong. Even then, the scale of theft is limited to one person and not happening on an industrial scale.

Re: From where I left

#87
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…

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.

Re: From where I left

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

This is a great point, it'll probably take the better part of the next decade for all this to shake out. It'll be interesting to see where it goes.

Re: From where I left

#89
Hesitating to put this because it's not related to the topic at hand, but I find monospace font for blogs hard on my eyes. I think I'm getting old, but Arial (and other sans-serifs) are easier to read.

Re: From where I left

#90

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

Dropping by in the comments to say many thanks for both of these books.

I have hardcopies of both and "Crafting" remains my all-time favorite programming book.

It's delightful, educational, and beautiful.

Post reply on HN