Comment by tptacek

That's entirely app-level issue; the frameworks and the system itself is perfectly capable of handling this. [1]

It's just that for _most_ cases it's perfectly fine to make the users wait until the animations is finished, and handling users tapping multiple things in a quick succession can get annoying and unwieldy.

There are some apps when it's infuriating though, especially when they're quadruply badly engineered and _tie the internal logic state_ to the UI state.

As someone living in a country where I don't speak the local language, I swear at Google Translate engineers daily because I do a "swap the active pair of languages and then quickly launch the camera mode" combo _very_ frequently, and the selected pair of languages isn't actually updated _until the animation finishes_.

It's maddening. [2]

[1]: A quick demo: tap an app on a Springboard to open it, and very quickly swipe up from the bottom to hide it. You'll absolutely be able to interrupt the animation of it launching.

[2]: I'm actually sorta guessing that this is a workaround for a different bug they had; when if you tapped this quickly enough a couple of times you could end up in a situation where the UI displayed a different pair of languages than the internal logic had, so they added that delay, but who knows, maybe I'm theorycrafting too much.

Window management on macOS is just trash.

3 people from my team recently switched to macOS and they never owned a mac before and they are all complaining about window management.

Do you know how dumb it makes me feel to have to tell them they need to install third party apps just to make their system somewhat usable? it's insane.