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

131–140 of 472 posts

Re: From where I left

#131

Post by munificent »

codazoda wrote: post #113
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,…

Would Game Programming Patterns help someone who wants to build a slot machine? I’ve built a wall mounted machine for my home but I never got the software side done. I think a book could help but most of them cover very different mechanics these days.

Honestly, probably not. It's about software architecture for games, and not about game mechanics specifically.

Re: From where I left

#132

Post by munificent »

braco_alva wrote: post #76
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,…

"Game Programming Patterns" has been of huge help throughout my career and it's always my go to recommendation for new game programmers and reading your comment makes me feel even more grateful that you made the effort of writing it, thanks for writing such a great book!

You're welcome!

Re: From where I left

#133

Post by munificent »

nyarlathotep_ wrote: post #90
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,…

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.

You're welcome! I'm glad you enjoyed them. :)

Re: From where I left

#134

Post by crote »

antirez wrote: post #82
simonw wrote: 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…

With open-source software, a license is as much a social contract as it is a legal one. People contribute because they want to be part of a community building something which is beneficial to everyone. Everyone contributes where they can, and in turn takes what they need.

Redis Ltd. broke the social contract. They decided that the short-term profitability of the company was more important than the project as a whole, the community which had grown around Redis and the future of the software. Probably a wise decision from a business perspective, but that doesn't make it any less of a rug pull from a community perspective.

You're right that no pre-relicense code was lost. People could and did fork. But something far more valuable was lost: the community's trust. First they relicensed the code solely for their own benefit, now they tried to take over third-party libraries and started behaving in a hostile way towards the community forks. Why would anyone volunteer their time and effort when it is mainly going to benefit a company which is so openly antagonistic against its volunteers? After all, what's the next shady move going to be?

Re: From where I left

#135

Post by munificent »

MisterTea wrote: post #115
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,…

It's because the audiences for each are different. The audience of programs are CPU cores that have a well defined set of behaviors. An i7 isn't going to one day decide it doesn't like the SHL instruction or offended by having to perform too many MOVs. The human by comparison is more taxing to write for as your brain is the compiler and checker for the instructions of your language. You write, proof read, correct, pr…

It's that but even more so: you aren't writing for a single human, but for the superposition of all possible readers of the book.

It's sort of like trying to write a program that is simultaneously valid Perl, C, Ruby, etc.

Re: From where I left

#136

Post by antirez »

PeterZaitsev wrote: post #121

Hehehe, Reading between the lines. Redis is Hurting, Valkey is making a real difference at pulling the customers away. Elastic and OpenSearch were in similar situation, so Elastic went on to change license back to (more restrictive) Open Source License. Redis went different route by bringing Redis founder back. I wonder if they go back on their license change next or do they think Redis founder endorsing license chan…

Except this is not true: I mean, I asked to rejoin, not because I evaluated the situation of the company, but since I wanted to do more hacking / community stuff. So you see what happens trying to read too much between the lines? That you invent what satisfies your needs as a reader, but drives you away from what actually happened. P.S. at Redis they didn't expected this at all and were really surprised.

And about switching to a more open license, who knows? Maybe we will be doing that as well if it offers enough protection - I'm not in charge for such decision but... I can suggest things -, so thank you for the idea (kidding apart, I was already talking about this possibility inside the company).

Re: From where I left

#137

Post by stackskipton »

BeefySwain wrote: post #130

All the conversations about SSPL seem to go the same way: - Someone complains about the extra restrictions imposed on AWS (lets be real, it's basically just about AWS) - People point out that SSPL is basically AGPL+, and that for the vast vast majority of people it doesn't make any difference - People counter that the SSPL is written ambiguously/untested in court, and so while it might seem like it's AGPL+ and doesn'…

Problem comes down to, what is cloud provider?

My company has a piece of software we will sell you that requires Redis/PostGres. For fee, we also offer hosting of said software. Are we now a service provider? Our software does come with ability to manipulate the data in Redis so do we have open source our entire code base? Would we get stuck in lawyer battle royale?

We have resellers coming on board so interface is being built that lets them deploy our software for their customers so Redis will be deployed by us and given to reseller? Are we cloud provider then?

Now, I think reality is Redis wouldn't see as cloud provider because we don't go "Here is Redis, do whatever you want." Lawyers however get paid to think of worst thing that could happen and our lawyers said "Eh...... I'd hate to have these terms hanging over your head."

That's why alot of people recoil at SSPL.

Luckily, Valkey is drop-in replacement for us, testing is almost completed and likely we will switch when paperwork is all completed.

Re: From where I left

#138

Post by [deleted] »

simonw wrote: 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…

[deleted]

Re: From where I left

#139

Post by ndiddy »

zokier wrote: post #106
antirez wrote: post #84

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

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

I believe that the original reason why they didn't just say "you're not allowed to provide this program as a service" is that MongoDB were trying to get SSPL approved by the OSI. The OSI didn't approve it because as you mention, it's basically impossible for a cloud provider to actually attempt to comply with the SSPL. Not only would they have to release the code to all software used to make the program available, they would have to do so under the SSPL. I'm not sure why MongoDB didn't change the wording when they gave up on getting the license classified as "open source".

Re: From where I left

#140

Post by thebiglebrewski »

Just wanted to acknowledge the humanity of antirez. To many of us, they're a folk hero, but they're just a normal human being with a family who wants good things for the world and their family.

Thanks for opening up to us so much and for what you've contributed to the world antirez! And welcome back!

Post reply on HN