The reason "2.4 GHz wireless" is an option is the very proprietary standard right there, or rather the static pairing coming with it. The absence of Bluetooth connection negotiation/switching/… removes an entire class of bugs and annoyances.
Bugs and annoyances which not everyone is having. Stripping out functionality to crush bugs is like removing your stomach to get rid of a stomach ache.
There are cases and classes of hardware where Bluetooth is not ideal and 2.4GHz proprietary standards are used (low latency audio, gaming mice, concert/conference audio. etc.) but those devices already exist on said proprietary standard instead of Bluetooth since they're usually not meant to be paired with changing hosts/clients all the time like most bluetooth devices, so what's your point? Do you want proprietary dongles to ship with every pair of earphones?
2.4GHz proprietary standards are no magic silver bullet either. Sure, compared to Bluetooth they can have the advantage of latency and bandwidth depending on how you implement said custom protocol in firmware, but it's ultimately the same damn overcrowded ISM band shared with the billions of devices everyone has everywhere (Bluetooth phones, smartwatches, headphones, cars, IoT devices, security systems, and, the 400 pound gorilla in the room, motha-friggin-Wi-Fi) . So due to pollution on the 2.4GHz spectrum you'll end up with potentially similar issues like Bluetooth devices except now you have a proprietary standard to deal with.
If you need good audio in one home location, then the dongle is just fine. My best audio, speaking and listening, is a gamer wireless over the head/around the ears thing with a microphone that can extend to where my mouth is that I bought off my son after he switched to some fancier thing with a YouTuber style mic. It has a base station that plugs into USB and also charges a second battery so I can talk and listen continuously. At work, sounding clear and not having your sound break is quite useful. Also for online games. If it’s just pod cast listening and yelling at kids to text when they get there or whatever, maybe it isn’t as important as these other features.
But also, in general, they say perfection is reached when there is nothing left to remove. Extra features often mean something is wrong with the design. Even with programming languages, it is vastly better for the default response to requested new features is “no.”
>If you need good audio in one home location, then the dongle is just fine
Well yes, for things that tend to stay in the same place no need use Bluetooth at all. Not denying any of that, but which of those are issue that have to do with Bluetooth?
>But also, in general, they say perfection is reached when there is nothing left to remove. Extra features often mean something is wrong with the design.”
Perfect is the enemy of good here. Bluetooth wasn't meant to be the perfect way of connecting devices, that's impossible, it was developed back in the late 90's for connecting millions of mobile devices to each other over a standardized, cheap (in terms of silicon die area) and most importantly, low power connection (batteries were small back then), and it does all that pretty decently. Sort of a jack of all trades master of none.
If you're looking for perfect solutions then you should be looking elsewhere and that's why proprietary solutions exist and there's nothing wrong wioth that.
