3 ms·
It's not the hardware that is struggling, but the software is getting more and more bloated. And by bloat I don't necessarily mean unwanted features, but more l
by not_your_vase 4y ago
It's not the hardware that is struggling, but the software is getting more and more bloated. And by bloat I don't necessarily mean unwanted features, but more like extraneous abstractions.
There is no free lunch, everything has a price. If you want to have fast, very efficient software, you will have to optimize it for the hardware, which will cost development time. It also may or may not be maintainable.
Or you can use an all-in-1 solutions, that will handle everything in all (most) situations. It will be relatively fast to develop with, but the result will be far from efficient. It will be "good enough" for the current hardware.
As long as hardware is cheaper than developer time, this trend will not stop most probably.
(On a personal note, this is my favorite thing about embedded software: developers are forced to use hardware efficiently, which can result in surprisingly fast code - at least surprising when compared to regular bloatware)
- adhesive_wombat 4y ago> embedded software: developers are forced to use hardware efficiently Getting less true in low-volume embedded, where you can now throw a few ARM cores (or now RISC-V) and GBs of RAM at it for just a few dollars extra. The payroll and time-to-market costs of paying embedded developers to lovingly massage and squeeze the application into the smallest device possible to save on the BOM don't start to pay off until you're shipping a lot of units.