This is a misconception that’s common among beginner C programmers. They think C is high level assembly and don’t understand the kinds of optimisations modern compilers make. And they think they’re hardcore and don’t make mistakes.

Hope you figure it out eventually.

even if you write in assembly, you still may not actually understand what is going on in the machine since processors convert the instructions to “micro-ops”, and let’s not forget hardware bugs like those caused by speculative execution

I’ve written programs in C. I’ve written programs in assembly, for x86 and for microcontrollers. I’ve designed digital logic and programmed it into an FPGA. I’ve built digital logic circuits with transistors.

I’ll still take Go over C any day of the week. If I’m doing embedded, I’ll use TinyGo.

CPUs are for people who don’t know how to melt their own sand into transistors.

Sand is for people who don’t know how to create their own silicon from hydrogen and a neutron emitter.

I wrote loads of firmware in c++ and some on highly constrained boards. You’re just stuck in the past and spewing bs

EL MAO

The obvious bait

CC BY-NC-SA 4.0

Forth is more like the real hardware language.