You know, while I do understand the reasons for the unstable kernel ABIs, that's actually what detracts me from personally recommending Linux unless if I know f

You know, while I do understand the reasons for the unstable kernel ABIs, that's actually what detracts me from personally recommending Linux unless if I know full well their needs. Even using printers is a pain (which I hope it will solve in the near future with standardised tools). Web browsing and web browsing only? Full speed! But beyond that, I'm not so sure that Linux will be ready. Plus while GNU and Linux user-level ABIs are stable, and LSB means that portability is nearly seamless (except if the GNU or Linux part is swapped itself), other APIs do break, especially when it comes to desktop elements. Snaps and Flatpaks accentuate the problem to the point that even if the system and app uses the same desktop environment (GTK on GTK / KDE-QT on KDE-QT), it looks like out of place. More importantly, Microsoft have focused on accessibility to the point that it can be navigated by keyboard, mouse or (recently) touch alone. GNOME settings (aka control center) don't navigate well on keyboard, not even allowing selecting search results (https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#g-c-c-and-orca https://www.debian.org/releases/bullseye/amd64/release-notes...).