.. but I don't think it means what the author thinks it means.
FTFA:
The Apple Calculator leaked 32GB of RAM.
Not used. Not allocated. Leaked.
First, AFAIK, leaking memory means you allocate it, but don't deallocate it. So how can he say "Not allocated?"
Second, leaked how? If it's leaking 32GB of RAM on, say, every keystroke, that would be serious; but if it allocates 32GB RAM once on start-up and simply forgets to deallocate it upon termination, it doesn't matter since the OS will reclaim the RAM for the entire process.
Today's real chain: React > Electron > Chromium > Docker > Kubernetes > VM > managed DB > API gateways.
OK, those are lots of layers of abstraction and they each use memory, perhaps a lot, and he has a point that modern software tends to use too many layers, but that doesn't mean that any of that memory is leaked: just used.
Based on that part of his rant, is he complaining more about the 32GB size of the (alleged) leak of the Calculator app, i.e., why should a calculator need 32GB? Sure, complaining that a calculator using 32GB is valid, but it's not a leak, just inefficient or lazy on the part of the programmer.