[dieulot]

Speaking of that annoying split, I have a base 2020 Intel MacBook Air and command-tab takes 200 ms to display, making it utterly unpleasant. Mind-blowing for a €1200 computer.

Are all Intel MacBook Airs affected by this? Only those with baseline processors?

[stnmtn]

Seems to me the intention is that if you quickly press command-tab to switch back to your previous window, you don't get the window popping up in front of that window you've brought to the front.

This is nice, as most of the time I'm command tabbing between two windows, so I quickly press it and no window pops up on my screen. If I need to press command-tab more than once, it appears and I'm able to select the window I'd like. Seems like decent UX to me

[dieulot]

I don’t think that’s it, no one told me about that when I complained about that delay on the Mac Power Users forums, and I can’t find anything about it (such as removing that delay) online right now.

Which Mac(s) are you experiencing that on, and since which OS version?

[stnmtn]

I'm experience what you described with a 200ms lag, and didn't notice it until you bring it up. On a 2020 Intel mac. After reflection, for the way I'm using cmd-tab 90% of the tab I prefer this slight delay as it doesn't block the screen when i'm switching between my browser/code editor, and when I need to press cmd-tab more than once, it's been 200ms and I'm able to press tab until I reach my desired app and I don't really notice that there was a delay

[mkdirp]

GNOME does this too. Their reasoning was exactly what your parent commenter said. I can't find a link now. Not that it's helpful to you, but there is a GNOME extension that does away with the 200ms delay.