Dynamic stacks with linked granular chunks? It consumes even less memory.

Not contiguous

Obviously chunk size is larger than class of objects to allocate.

This is not always possible

Then fixed stack also is not possible for such cases.

Sure it is? Stacks are contiguous

If you can't limit stuck chunks you can't limit fixed stack. And vice versa. It's quite simple.

It's bad analogy. webauthn is quite far from just a protocol to verify keys.

> Ask any SOTA agent to identify a specific type of "janky crap"

It's always total hallucinations. It could only see local minor issues.

It happily starts to introduce fake abstractions and other junior level "refactoring" making it even worse.

Am I missing something but tag in git says nothing about actual deploy. It's at most a deploy attempt. What's wrong with CD which tracks actual deploys and records which commits are deployed and all related info like who and where?

The point is libraries are agnostic. You as a library user provide io transport and loop implementation which supports/not supports cancelation. And you as as library user handle cancelation.

> Libraries swallowing cancelled() or libraries lying that they support cancelled.

For me former is obviously worse.

The most frustrating part about it for me it's Andrew's argument: just write correct code. I have C at home.

In the future, tooling can run those checks statically on IR.

Unfortunately, it you want to handle errors right, it's overly verbose, so no one really does it. That's my problem really. Even in the blog post snippet, I could have show well behaved code, because I'm well aware of it, but then the error handling would be more code than the part I'm trying to showcase. Static analysis will not help there.

In the future, it would be good to not need to require that unwritten tooling

I think the craze was about "purity" of mustache as presentation-only template engine. Apparently you need some level of logic to be useful.

Yey! Let's speedup project downfall to crap abyss even more!

You either care about project and do reviews. Or yolo vibe code. This middle ground has little sense.

Oh boy. There were (and are) hordes of enterprises requiring us to support SAML and were quite amazed to know Entra and all big auth providers perfectly support OIDC.

Oh gosh. I could only imagine how many apps in chain crafts and parses soap envelopes with adhoc code with mandatory info loss.

I dunno, looking back I don't think that soap was really the problem. I'd see people complain about how complicated soap was while not using a library for it. Then say REST was so much easier as they piped the JSON through eval to get things working.