[pizza234]

Certainly YMMV applies, however, it's important to distinguish the nature of the two cases.

Broken BT support in a Windows context generally means poor drivers for a given device - at least the Windows 10, which is almost 4 years old, has a stable BT stack. Therefore, BT problems are of particular (per-device) nature.

In Ubuntu, the problem is systemic, due to (even ignoring how terrible the BT protocol is) both Bluez's (alleged) terrible engineering practices, and Ubuntu's utter carelessness of the area. In this terms, BT problems are of universal nature.

For example, the 18.04 Pulseaudio/BT configuration is broken by default - see https://askubuntu.com/a/1050172.

This is not an exception; the Pulseaudio/BT configuration has been broken in a way or another since... forever. Very evidently, the Ubuntu devs prefer to ship a broken-but-up-to-date BT stack, than a working-but-old one.

For a more historical perspective of the Ubuntu/Bluez trainwreck, see http://www.bennybottema.com/2010/08/08/how-ubuntus-broken-bl.... Summary: "Bluez is a bunch of cowboy coders is why".