4 ms·
How did we get to a place where it's unreasonable to expect to change some text boxes within 50 million cycles?
by anonymoushn 4y ago
How did we get to a place where it's unreasonable to expect to change some text boxes within 50 million cycles?
- jfengel 4y agoWhen computers started doing a billion cycles per second, you can shift your whole mental organization to prioritize other things. You can waste a ton of the computer's time rather than waste your own debugging something the user won't even notice.
- anonymoushn 4y agowe can waste the users' time you mean?
- jfengel 4y agoMilliseconds at a time, sure.
- ZephyrBlu 4y agoThe real question is, for your application does it matter if some text boxes are rendered in less than 50M cycles or not?
- anonymoushn 4y agoYes, for every application.
- ZephyrBlu 4y agoThat is provably false.
- anonymoushn 4y agoDo you mean "people still use VSCode even though many interactions have unnecessarily high latency" or "people's experience using VSCode would not be improved by the elimination of these latencies?" Can you post the proof you are referring to? Here's some article about this topic: https://www.gigaspaces.com/blog/amazon-found-every-100ms-of-latency-cost-them-1-in-sales https://www.gigaspaces.com/blog/amazon-found-every-100ms-of-...
- ZephyrBlu 4y agoThe former. > Can you post the proof you are referring to? The fact that applications which use 50M cycles to render text boxes exist and are very popular is proof in itself. There is not a significant difference in the product if it uses 10M cycles (Or even less) vs 50M, as long as it is fast enough.
- anonymoushn 4y agoRight, everyone will use applications that are unbearably slow when there are no alternatives, and that's why we should not try to make applications that run at reasonable speeds.
- joshmanders 4y agoYou realize that the example you used is the top used tool in it's field and that field is littered with tools that have existed longer and are arguably faster? You know why VSCode is the leader? The tradeoffs of a little latency that can be annoying but mostly is unnoticeable is acceptable for all the added benefits the editor gives us.
- bastawhiz 4y ago"50 million cycles" is a meaningless measure far detached from the actual work being done. You're choice of front end framework has almost nothing to do with total CPU use: how the text box looks (rounded corners, drop shadow) has far more impact on cycles overall. But it doesn't matter. Cycles are not in shortage. CPUs are mostly idle. If something takes less than 16ms to complete, you simply won't notice.