bvrmn

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

Then fixed stack also is not possible for such cases.

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

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

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.

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.

Ahah. In my days SOAP libraries were kinda shitty up to the point I had to write my own to handle "non-standard" (actually very standard) WSDL definitions. SOAP consumption in one lang was okeish, especially Java or .NET. But interop — oh boy. The biggest issue were services exposing SOAP interface based on code-first approach, when you write some declarative code with annotations and library transforms it into WSDL and proxy endpoints.

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

You could take any pills and have any fantasies in your small coding corner. But saying very strong word "better" has very distinctive aftertaste.