I like Windows and Mac OS, but I feel like they have a long way to go before they're useful for my day to day work.
Everything I own and do is terrible on Windows and works fine on Ubuntu.
There is some weird finnicky things with Bluetooth headphones (especially headsets) but it is honestly such an easy fix (plug them in) that I don't even think about it.
Windows on the other refuses to connect at all to my Bluetooth headphones (Sony), my graphics card has broken drivers (and continues to) and that is even before I mention all of my gripes with Windows as a developer (compiling on Windows is basically a no-go)
The only thing I use Windows for is gaming, because unfortunately games are basically never released for Linux.
Indeed every time I think of getting a new laptop or desktop, I try to do research into how well Linux will run on the hardware. Thankfully there seem to be a decent number of laptops that have Linux preinstalled now.
As much as I enjoy tinkering, even after using Linux for a while I still don't have a strong understanding of how things work, and it's frustrating to be forced to tinker when my intention was to get things done.
Perhaps I need to dedicate more time to understanding how things work?
Just install Ubuntu. Ignore everyone saying Ubuntu is a kiddy OS ("All you need is X, Y, Z-ix"). Ubuntu is Linux Windows (not really, but it is pretty hard to mess up).
Neon or openSuse is more Windows-like IMO.
Stick with Debian and Ubuntu. And more Debian, going forward.
I use Debian for servers though.
Yes, if you don't already, learn basic command line very well, with stderr/stdin/stdout, pipes, sed, grep, find, cat, make, etc. etc. You'll then thrive in Linux, and it will help you with OSX, too.
I guess what I meant was more that I don't understand how Linux the OS works, not how to work in Linux?
For example, if I do something and it doesn't work, I want to see something that went wrong. This could show up:
1. In stdout/stderr 2. In a logfile specific to that software, somewhere on my computer 3. In an aggregated logfile somewhere on my computer 4. Nowhere, but will do 1, 2, or 3 after you enable something in a config file or cli parameter
This all assumes that if there's something you have to look up (like where it logs files to), you can figure it out based on the man page or website or inspecting your filesystem, and then it actually logs some actionable information on the problem.
I've just come to terms with the fact that everything, no matter how simple it should be, is an ordeal the first time I do it. I just set aside time to research and make notes.
I find that sort of behaviour far more worrisome than a bluetooth headset not working.
Have you tried to intercept the traffic?
I was an early adopter and it was a bumpy start for sure, but you expect that. Just wait half a year or so after a new processor generation and it'll be fine. Zero issues on my Haswell laptop for the past years.
Intel has full-time people working on the Linux graphics stack. I've contributed bug reports and stack traces and they have been super friendly and responsive.
TLDR; If you want good hardware support without worry, buy from a Linux vendor.
My system76 laptop also had an obnoxious firmware bug (that seemed to only effect linux) with the media keys that they basically told me they couldn't do anything about: https://www.youtube.com/watch?v=52TaFzCDDkA
Linux desktop environments and software also have serious QA issues in general IMO. When running linux on the desktop I found myself spending more time reporting bugs than actually using my computer. I really enjoyed tinkering with linux, but when it comes to day to day use (particular on laptops) I found that the quality and reliability just wasn't there.
I ended up running windows on my system76 machine and eventually moving to a macbook air.
Maybe I'll try again in a few years :(