What's wrong with embedded C? Would you rather write assembly?
leo85811nardo
joined 1 year ago
From my understanding, one of the actual use case of assembly is for cyber security engineers to dump assembly instructions from a compiled program, so they can check for any potential vulnerability. I've also seen assembly included in an embedded codebase (the overall project is in C), which I assume is for more optimized performance and deterministic behavior
Maintainability is inverse correlated to job security anyway
Ackchyually, value watching in debugger almost guarantee to get the value by address, but printf in some languages can pass by value, unnecessarily make copy of the watched variable, and the value printed is the copied data instead of the original
They used Arch forum. The reason it took a while because someone just left a link to a long wiki without any comment on where exactly to look at
In my opinion, it's bad either way for different reasons
If they do tell the difference, then there is some tracking built into the machine that runs the engine, which is bad for the application user
If they don't tell the difference, then there will be exploits for intentionally reinstall multiple times, which is bad for the application developers
All of the quirks you said are true, yet they still established the "okay" ecosystem of hobby-grade microcontrollers like Arduino, IoT devices, and other small scale robotics systems. None of them would have happened without the "okay" abstraction C/C++ provides as opposed to assembler