Comment by vanderZwan
10 hours ago
Another reminder of how easy it is to forget how ridiculously fast computers are these days (especially when you're like me and not writing stuff close to the metal for your day job).
10 hours ago
Another reminder of how easy it is to forget how ridiculously fast computers are these days (especially when you're like me and not writing stuff close to the metal for your day job).
And how ridiculously slow software is. Unless you are doing bulk processing most task should be ready in milliseconds.
In terms of throughput, absolutely.
In terms of latency... well... we also could do a lot better there, but as I understand it, even if you do your best to cut away as much software bloat as possible, the latency "floor" seems to be higher than in the old days[0]. And the many layers of abstraction that is the average software stack don't help. Like, I'm doing my best to keep a web-app snappy, but there's only so much you can squeeze out of a browser.
[0] https://danluu.com/input-lag/
Latency can be reduced with removing the memory management-as with uclinux- https://github.com/EI2030/FemtoTX/blob/gh-pages/uclinux_intr...
But chips today are much larger and are basically a cruise ship or an aircraft carrier- bigger with more work than a bike. https://www.inkandswitch.com/slow-software/
https://youtu.be/oE4cbIP5ieQ?si=h1I51dWw5w-OulVs
Actually latency is way less of a problem, if the input is buffered, as you can just type ahead.
1 reply →