5 ms·
Only if we stop worshipping at the altar of speed. We are collectively so obsessed about maximizing speed related metrics that simplicity often takes a backseat
by dman 10y ago
Only if we stop worshipping at the altar of speed. We are collectively so obsessed about maximizing speed related metrics that simplicity often takes a backseat.
- vvanders 10y agoSpeed = battery life which I for one find somewhat important.
- dman 10y agoAgree with you on that front. In fact on my laptop i would happily trade some latency/responsiveness to get battery life. ie let the os batch some wireless / IO / computation together and do it at one go when it wakes up relevant hardware from its sleep state.
- vvanders 10y agoModern hardware is actually really good at DCVS. You don't trade latency for battery life, just doing less work gets you better battery efficiency. There's a really gnarly V*I curve which is not linear(as clock speed increases, voltage also needs to come up) which makes good performance even more key.
- slededit 10y agoIf anything I'd argue we see the opposite. Billions of cycles are wasted through abstraction vs the few that do actual work. You'll see this profiling any modern application; extra copying, useless computation and other ills abound. Copying data and computing things "just in case" make the software much easier to modify. But it is not a good way to maximize "speed related metrics".
- mrich 10y agoI feel like speed often takes the backseat, especially in large big corp projects designed by committee. At the end during user testing everyone realizes the architecture is just too slow and all to often this leads to a failed project.
- Dylan16807 10y agoCollectively, we don't have to change anything. A coder today can already avoid 99% of this complexity with some full memory barriers and message passing.