Wait till bro find out the program written in the "memory safe language" depends on many libraries written in C

Last time I tried Virt manager, I couldn't figure out bridge networks and ended up corrupted the XML config for the VM. Skill issue for me I guess

I just looked them up and maybe you are right. But QEMU definitely lacks a GUI config tool that is both easy to use and allows for advanced features like snapshots. So far the only ones I know is GNOME Boxes and Virt Manager, and neither is as good as providing handy ways to configure as VirtualBox. I could probably just write the XML config or QEMU command by the documentation, but next time it could be a different scenario so I have to investigate the docs and maybe a few more forum posts. In VirtualBox, the buttons that do everything for me are always there

Because they are for different use cases. I use QEMU+KVM on desktop for games and 3D CAD software, because of its undeniable performance advantage. But on work laptop, I use VirtualBox to test my software on different platforms. On VirtualBox it's relatively easy to initialize a VM, configure network, file sharing and device passthrough, and its snapshot feature allows me recreate the same environment for troubleshooting

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

Over the beginning few years into software engineering and FOSS world, I legit thought Sourceforge is a sketchy software download website

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

Because the machine could be headless so it can't display the applet to click on

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

Having to adapt to shells is exactly why I don't like to use radical shells like fish or nushell. I don't want to feel too comfortable with them, because if I do, I would probably regret it when I'm stuck in situations that doesn't have the correct shell. SSH into a new server or Raspberry Pi that has DNS issue, for example, which actually happened to me more than once. The DNS is already troublesome, and I don't want shell unfamiliarity to become another headache

If you use zsh, there is zsh syntax highlighting plugin. For bash, a cursory search gave me ble.sh which looks interesting. And as other threads have mentioned, fish shell has this built in, but beware fish shell syntax works drastically differently from other POSIX shells