Performance Matters (2019)

Post by setr » Thu, Nov 26, 2020, 6:14 PM UTC

TeMPOraL wrote: post #60

jspash wrote: post #58

Earlier quoted context omitted.

I would argue that the 250ms lag mentioned in the article was not the reason the ePCR system was perceived as being slow. Consider the new trend in login forms these days whereby you are forced to enter you username or email THEN press a button THEN enter your password THEN press another button. What used to be simple is now no longer simple. Why is it like this? To accommodate the x% of people who seem to get confus…

> Why is it like this? To accommodate the x% of people who seem to get confused in some manner when presented with "too many choices". FWIW, this is done to accommodate SSO (single sign-on), which matters for any software that's going to be used in corporate or governmental environments. You have to submit your login first, because it's used to determine what authentication method and provider to select. That said, I…

Post by doctor_eval » Thu, Nov 26, 2020, 9:15 PM UTC

branko_d wrote: post #68

doctor_eval wrote: post #63

Earlier quoted context omitted.

I had a similar experience using my own web app over a satellite link (750ms+ latency) many years ago. What took minutes at the office literally took hours over the air, which I found really surprising. I knew it would take longer but it was much more than 10x longer. This was when I first realised that UI delays have a non linear effect on productivity. The productivity loss from 10x latency increase is more than 10…

Indeed, this non-linear effect of UI latency on productivity is real, and has been studied/known for decades. I think the "The Economic Value of Rapid Response Time" from 1982 is rather illuminating: https://jlelliotton.blogspot.com/p/the-economic-value-of-rap...

Post by renox » Fri, Nov 27, 2020, 4:23 PM UTC

bsder wrote: post #25

obviouslynotme wrote: post #12

I'm old enough to remember Win32 programming in C/C++ because it was the only thing that worked. There was a problem though. Memory management, shitty standard library, and a non-existent packaging system. Java came around and gave you something that worked. Memory management? The runtime does it. Want to do X? Here is a library for X. These combined with academia moving over to Java killed new C++ development hard.…

> Memory leaks are honestly not even a problem unless you have long running servers. Firefox is a counterexample to this statement. Rust appeared because experienced Firefox developers simply couldn't manage C memory manually, C memory with garbage collection, C++ memory manually, or C++ memory with garbage collection.