3 ms·
Classic Mac OS always perfectly queued any number of input events and executed them in order exactly as expected, regardless of how much the system was lagging.
by HyperTalk2 8y ago
Classic Mac OS always perfectly queued any number of input events and executed them in order exactly as expected, regardless of how much the system was lagging. None of the input would be silently discarded or mishandled like it is today. You could easily do something like this:
>type command-N to create a folder
>type its new name "abc"
>type command-O to enter folder "abc"
>type command-N to create another folder within folder "abc"
>type its new name "123"
>type command-O to enter folder "123"
>change mind and type command-W and command-delete to put folder "123" in the trash
>type command-shift-W to close all windows
>type "Macintosh HD"
>type command-O
>type "Applications"
>type command-O
>type "Adobe Photoshop"
>type command-O
>type command-N to create new Photoshop document
>type command-S to open the save dialog
>type command-D to navigate to desktop
>type "abc" to select your new folder
>type command-O
>type the return key to save the new document
It doesn't matter whether the system was able to keep pace with your input. You were guaranteed to have a new folder named "abc" and your new Photoshop document already saved inside.
Now in OS X (I'm sorry, "macOS"), you need to pause at every step and wait until it's done executing before doing the next. Otherwise your input will be lost in the multithreaded abyss.
I hate it.
- saagarjha 8y agoI don’t think it’s macOS that’s dropping your keyboard events, rather, they’re being forwarded to the old application or nowhere at all while you’re transitioning.
- pjc50 8y agoYes, but that's kind of the point - the system as a whole loses events, it's no help to the user to abdicate responsibility for that. Especially if there's no way to fix it without redesigning the system.