I haven't had to find a Linux Wi-Fi driver for a single piece of hardware made in the last decade.
The hardest thing about running Linux is video drivers, and AMD's are in the kennel now, and Nvidia's are nearly always up-to-date and in the package repository.
I use Windows, wsl and native Linux as a software dev. Linux gives me more problems than wsl, gives me more problems than Windows. I must say Windows is the slowest (especially booting and the file system), but the tools, drivers and user interface are much more stable.
Just a few days ago I managed to brick the Gnome terminal by upgrading python in Linux. Bing AI to the rescue to ctrl-alt-f7 / vim / i / :wq me out of that situation. And some more symlink re-patching.
Dll's versus shared objects: linking I find a true maze in Linux land. Anybody else needed rpath (hard code search paths in binaries) to make sure the shared objects were found?
I once got an unconfigured Windows terminal because of a windows upgrade over a duration of 7 years or so. It at least gave me a terminal window to work with.
That said, I don't trust fully the auto synchronization of SharePoint and friends. Most important stuff is checked in into a server that hosts git.
I have to say this was for linking against a third party driver and there appeared no other way around. But my point is that at link time there is knowledge needed about the location of the shared object itself. https://tldp.org/HOWTO/Program-Library-HOWTO/shared-librarie...
The hardest thing about running Linux is video drivers, and AMD's are in the kennel now, and Nvidia's are nearly always up-to-date and in the package repository.