- UI non-responsiveness: it is extraordinarily frequent that I will chord a tab change in Safari or in iTerm2, and the system will not respond for sometimes multiple seconds. It's the same with creating tabs in Safari. ⌘-t or ⌘-{ do not respond.
- Application switching focus failures: ⌘-tab will raise another window, but window focus will not follow. This has caused me to lose work. ⌘-tab, ⌘-w will sometimes close an iTerm2 tab that's behind the Safari window I'm looking at.
- Mouse pointer lag: Probably related to the input lag above, the trackpad will not respond for multiple seconds after I begin touching it. If I "wake" it with a two-finger scroll, it will often lose half the input and instead click.
- AirPlay stuttering: even two ethernet-wired systems will still lose data between them. It's a crappy experience.
- discoveryd: My Apple TV's network name is currently "Apple TV (5)". Macs sometimes do this too.
- Slow laptop wakeup: I almost always have to tap a keyboard key to wake the display after opening my laptops (MBr and MBPr). Almost always. But not always.
That's just off the top of my head. Many of these have followed me between OS X revisions and different hardware. It amazes me that such bugs stick around.
>UI non-responsiveness: it is extraordinarily frequent that I will chord a tab change in Safari or in iTerm2, and the system will not respond for sometimes multiple seconds. It's the same with creating tabs in Safari. ⌘-t or ⌘-{ do not respond.
Ok, for this I can't say much, because every since 2010 or so I've used Chrome in place of Safari. As for iTerm2, I've tried to switch to it several times over the years (later mostly because of Tmux integration) but always found it to be buggy and reverted to the Terminal.
>Application switching focus failures: ⌘-tab will raise another window, but window focus will not follow. This has caused me to lose work. ⌘-tab, ⌘-w will sometimes close an iTerm2 tab that's behind the Safari window I'm looking at.
Hmm, haven't seen this -- and I use ⌘-tab and the ~ variant heavily.
I have seen lagginess in focus when switching full-screen apps use, and I sometimes start typing before that happens. This got a little better in 10.11 though (either faster focus switch or less transition time).
>- discoveryd: My Apple TV's network name is currently "Apple TV (5)". Macs sometimes do this too.
DNS issues I've had (and mentioned in another comment). They tried a transition to a new DNS backend which was buggy. They reverted back to the old one with 10.11 (or sometime in 10.10.x) though and has been OK since then.
>Slow laptop wakeup: I almost always have to tap a keyboard key to wake the display after opening my laptops (MBr and MBPr). Almost always. But not always.
Do see this from time to time (though it almost always works in my case).
Could be a sensor issue though -- not a software thing (the display up sensor not registering, but tap working ok).
Just a quick nitpick: discoveryd was reverted on the last release... OSX is back using mDNSResponder again. You can't really say "It amazes me that such bugs stick around" if you're not actually on the newest version.
- UI non-responsiveness: it is extraordinarily frequent that I will chord a tab change in Safari or in iTerm2, and the system will not respond for sometimes multiple seconds. It's the same with creating tabs in Safari. ⌘-t or ⌘-{ do not respond.
- Application switching focus failures: ⌘-tab will raise another window, but window focus will not follow. This has caused me to lose work. ⌘-tab, ⌘-w will sometimes close an iTerm2 tab that's behind the Safari window I'm looking at.
- Mouse pointer lag: Probably related to the input lag above, the trackpad will not respond for multiple seconds after I begin touching it. If I "wake" it with a two-finger scroll, it will often lose half the input and instead click.
- AirPlay stuttering: even two ethernet-wired systems will still lose data between them. It's a crappy experience.
- discoveryd: My Apple TV's network name is currently "Apple TV (5)". Macs sometimes do this too.
- Slow laptop wakeup: I almost always have to tap a keyboard key to wake the display after opening my laptops (MBr and MBPr). Almost always. But not always.
That's just off the top of my head. Many of these have followed me between OS X revisions and different hardware. It amazes me that such bugs stick around.