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

What’s wrong with embedded C? Would you rather write assembly?

While I do see most of the listed stuff happened to me before, they only appear once in a while and it’s often just one sentence in the list is true. I think OP is trying to make an exaggerating slander where it’s extremely unlucky to have more than 5 sentences is right

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

Extensions are not equivalent to native customization, and both have pros and cons. On one hand, extensions provide a variety of features that can be added specific to people’s likings, but on the other hand, there are chances of incompatibility (in gnome shells for example) and delayed maintenance from developers (which results in having to wait for them to finish the work when dependency updates)