Re:Why Thomas Cook Collapsed
by NeedMoreTea on Thursday September 26, 2019 @08:01PM
(#21087032)
Amiga's pointer was a hardware sprite, so that always stayed responsive. Was more thinking of the OS's themselves rather than within applications. You could certainly get Amiga to slow down in the apps, particularly if you were programming it badly. As it generally only redrew when needed and managed layers and viewports pretty well, getting it that laggy would have taken effort. :)
Took years after I abandoned the platform for serious use for Windows not to always be more sluggish, and get dramatically worse when under load. Course by then I was on '040 comparing with Pentium something.
Re:Why Thomas Cook Collapsed
by mixmastamyk on Thursday September 26, 2019 @08:27PM
(#21087223)
Definitely could be poorly written exceptions. There is a good post here describing keyboard latency on old computers.
Re:Why Thomas Cook Collapsed
by dreamcompiler on Thursday September 26, 2019 @10:12PM
(#21087798)
This is especially egregious on mobile because it's much harder to point at anything accurately with your finger.
The Mac mouse pointer was always responsive due to interrupts, but that didn't mean that what you clicked on was.
However, the thing that I hate most about the modern web and similar UIs is that they reflow or otherwise move the content you are looking at after you click and before the click is mapped to an element, so you don't get what you click or tap on. This is absolutely unforgivable in my opinion, and absolutely not a matter of degree or grey areas unlike most of the things people complain about.