2 ms·
> Apple doesn't have to listen to what the developers want--they don't need your business anymore. Maybe, and maybe not. For example, I bumped into an issue w
by bsder 10y ago
> Apple doesn't have to listen to what the developers want--they don't need your business anymore.
Maybe, and maybe not.
For example, I bumped into an issue with the older MBP where if you plug in a Universal Audio audio interface and a 4K monitor, the audio interface starts to hiccup. The 4K monitor moves too much data over Thunderbolt in a single transaction and so overruns the latency limits for the audio interface. I had to solve this by putting the 4K monitor on the HDMI.
So, what "end user type" is going to figure this out? Universal Audio somehow missed this--nobody doing audio driver development on 4K monitors, possibly--and likely couldn't do anything about it anyhow. Apple likely missed this because it's just a couple of people. Most end users just return the audio interface with a "doesn't work".
The fact that everybody missed this means that Microsoft now has a windows of opportunity in audio. They have a gigantic touchscreen with huge resolution. If they didn't mess up and they separated the interfaces, they have a clean run to displace Apple in the audio space for years.
These are the kind of things your developers run down. Piss them off at your peril.