> No one likes to wait for the computer to respond.
Ha, you wouldn't know it from using a modern computer interface. I have a hobby of counting the seconds since when I click something on my phone, a computer more powerful than supercomputers were in the 2000s, and when something actually happens. It is often in the double digits.
This may even be a result of the thing you're describing: our desire for speed has bled into our 'productivity' as developers, leading us to sacrifice the user experience for the sake of (theoretically at least) building an application faster. Though honestly, I'm not convinced that's actually happening because we've introduced so much complexity in our effort to automate as much as possible that we've actually just made everything much worse.
Yeah, Microsoft Teams occupies 2Gb of RAM at start and switching between "chats" takes a hefty 15 seconds ALL THE TIME. I developed PTSD at the very thought I gotta change to a different channel.
Ha, you wouldn't know it from using a modern computer interface. I have a hobby of counting the seconds since when I click something on my phone, a computer more powerful than supercomputers were in the 2000s, and when something actually happens. It is often in the double digits.
This may even be a result of the thing you're describing: our desire for speed has bled into our 'productivity' as developers, leading us to sacrifice the user experience for the sake of (theoretically at least) building an application faster. Though honestly, I'm not convinced that's actually happening because we've introduced so much complexity in our effort to automate as much as possible that we've actually just made everything much worse.