2 ms·
It's always something else doing something wrong. Everything has to conform to Apples design guidelines. Heaven forbid the OS could let you chose what you want
by okamiueru 3y ago
It's always something else doing something wrong. Everything has to conform to Apples design guidelines.
Heaven forbid the OS could let you chose what you want to happen... like launching Spotify instead, or simply nothing at all...
It's the headset doing something wrong. What a fascinating take. You wouldn't happen to be working at Apple R&D?
Maybe I missed the /s, it's just too on the nose, almost as if you're ridiculing it.
- hollandheese 3y ago> Heaven forbid the OS could let you chose what you want to happen... like launching Spotify instead, or simply nothing at all. Yes, the OS could do that. I'd prefer if Apple made that key configurable. But the problem isn't Apple and Bluetooh Headsets, it's that Apple made the play/pause button unconfigurable (without additional software). >It's the headset doing something wrong. What a fascinating take. You wouldn't happen to be working at Apple R&D? IT IS THE HEADSET DOING SOMETHING WRONG! No one asked it to send play when it connects, the manufacturer decided to do something brain dead there. It still messes with Windows and Linux machines too if you set the play/pause button to launch an app. Do you happen to work for a bluetooth headset manufacturer? It sure sounds like you're excusing their broken behavior.
- okamiueru 3y ago> But the problem isn't Apple and Bluetooh Headsets, it's that Apple made the play/pause button unconfigurable (without additional software). Compare it with > - Don't like that apple's "Music" app pops up when you connect a Bluetooth headset? => Install an app The only difference is that you add a puzzling self contradiction of "the problem isn't Apple, but that Apple has..." This is entirely an Apple and MacOS thing, and most certainly not an issue on Linux. Though I don't know about Windows.