3 ms·
That depends on the application and the use case, but good performance and good readability aren't mutually exclusive. Easy to read software might not always be
by rezonant 3y ago
That depends on the application and the use case, but good performance and good readability aren't mutually exclusive. Easy to read software might not always be the most performant, but it's far easier to improve performance in an easy to read codebase than it is to make a hard to read but performant codebase easier to read.
- krab 3y agoYeah, that's right. I just feel that latency is sometimes missing from the discussions re. developer efficiency vs paying more for compute.
- josephg 3y agoYep. Theres a huge experiential difference between something happening instantly and it happening in 200ms or so. Especially when typing or playing video games.
- krab 3y agoIt's everywhere. Next day delivery vs in a week. Streaming vs DVD rental. CI jobs. Notification about relevant news for stock traders. Switching files in editor. Jump to definition in IDE. Typing and videogames you mention have a very tight latency budget. If you don't fit in the budget for the specific task, your product features don't matter much.
- collyw 3y agoI see far more examples of per premature optimization (resulting in horrible code) than performance problems.