This is a common thing and the reason behind avoiding pointers to register-sized values across function boundaries. An add10() that returns the value added by 10 is better than the one that mutates through the pointer. Totally fine if inlined though.

If we forbid the inlining, the caller is forced to put i on the stack

str r0, [sp, #4]

to pass the ptr to add10

add r0, sp, #4 // put the ptr relative to the stack ptr on r0 before call

then the value is loaded from the stack into r1 before the printf call

ldr r1, [sp, #4]

It’s only a 20-ish% increase from June in Brazil, so I’m securing mine before they have to renew their inventory and increase it even more.

Oh, second ed is out already?

De longe

It's annoying in C++ to query an std::unordered_map<std::string, T> when what you have is a std::string_view (pointer, "borrowed") instead of the std::string (allocated on the heap, "owned").

Add to Playlist gets worse every month or so

Wondering if this is the kind of thing that @welltypedwit.ch will say is not good in practice.

There is a nice online demo/playground: se-tuebingen.github.io/oopsla-2025-...

100% this!

Scary how completely unconcerned they are with re-election. Final years of the term will be devoted to diminishing the electoral system itself.

I had these before moving to the Microsoft Sculpt. Sculpt is not as durable as this one, but this keyboard is way too big and takes over the whole desk. Happy with a mechanical split these days.

In a 100 years, people will be talking about these companies like we talk about IBM during WWII.

It’s really sad to see people still doing this at this point. It’s as if they get a high from figuring out the hypocrisy.

I love how he said he doesn’t feel bad for being somewhat disconnected from the current developments of AI because he is paying much more attention to what thinkers in other areas are talking about cognition and learning.

e.g. compression and crypto algorithms are very sophisticated, but if you hide that in the HTTP stack, people working on a web app don't have to understand their details when implementing applications.

I'm not a fan of the approach, but I've seen very pedestrian codebases survive and succeed a lot more than the codebases that had sophisticated constructs that got perverted by changes. Note that sophistication is not forbidden. It's requiring everyone to understand it to work on the project.