A long time ago, there was an editor called Brief (designed by Underware) I loved. It worked great, right until version 3. It slowed way down because they added some new tricks. When I noticed this and talked to the developer, his response was "get a faster computer."
I'm quite the opposite. I design software that runs fast on tiny Raspberry Pis because it's very possible, but it takes knowledge to do. Instead of buying fast hardware with 32 cores and gigahertz CPUs, fast DDR RAM, I buy cheap, ubiquitous commodity hardware.
I will add, part of the problem is hardware cost. People tend to virtualize computers into tiny Docker VMs. Now you've taken that super powerful computer and stressed it so it's running a huge AKS cluster of many small virtual machines.
AVR (which Arduino uses) is pretty fun. 8-bit RISC, tens of K of flash, and still programmable in C with just gcc and avrdude to flash it. Mostly on-the-metal stuff (no room for an OS).
Docker is so light compared to the apps that run inside the containers. It mostly isolates groups of processes from each other, in terms of memory, network, filesystems, etc. but the containers are all running under the same kernel (and thus the same device drivers). Very different from the thick layer that actual virtualization stacks bring like vmware / vbox.
Sure. But when you hundreds or thousands of small containers....
(post is archived)