You say KDE hangs, but what component hangs actually? It it plasmashell (other apps work but panel is dead?)? Kwin (windows move/respond to input?)? KDE apps?
I would suggest you to install a distro with kde (fedora KDE edition or open SUSE, not neon) if you're not confident with administration. Use something like Kinoite for accidental breakage protection, or if you want to keep /home as is, install fedora 42 inplace (the new installer).
Not only my experience but also that of many KDE devs say that fedora KDE is probably the best mainline KDE experience (ignoring niche distros or customized KDE).
Also, don't use xorg session. Always log in to default wayland session unless you have incompatible usecase (in that case you know what you're doing).
Yes it is possible to create disposable-isque api keys for different uses. The monetary cost is the cost of privacy and of not having hardware to run things locally.
If you have reliable privacy friendly api vendor suggestions then do share. While I do not need such services now, it can a good future reference.
Nope, these services almost always require user login, eventually tied to cell number (ie non disposable) and associate user content and other data points with account. Nonetheless user prompts are always collected. How they're used is a good question.
Cut the crap. Flatpak uses hardlink from repo where file names are jash of the file itself. The chance of duplication is exactly same as that of duplicate files of same name in same directory.
Flatpak repo grows because we trade uncertainty over abi stability with installing all needed versions of libraries. For abi incompatible builds you could already do that in many distros (versioned soname) but to a lesser extent.
Also I usually do not install nvidia GL with flatpaks that I won't run on nvidia on hybrid gpu laptops anyway for energy reasons.
Contributing to AOSP is already difficult. Now patches wrt stable branch will lead to more conflicts as stable gets older.
Why are parts of Android developed in private?
It typically takes more than a year to bring a device to market. And, of course, device manufacturers want to ship the latest software they can. Meanwhile, developers don't want to constantly track new versions of the platform when writing apps. Both groups experience a tension between shipping products and not wanting to fall behind.
I do not get what you're trying to say here, sorry.
On the note on similarity I mean macos userland is closer to bsd than linux. Also for normal usage freebsd is much different in nature than usual linux (free)desktop though they share same desktop shells which isn't the case for macos either. And while most people aren't writing with posix api everyday, many (most?) paradigms translate to win32 so that the crt from mingw works well. It matters only if you're working with msvc toolchain, and then you've to adapt to windows-isms.
Personal anecdote: yes I find macos more familiar than windows even though I use windows vm often and macos rarely. At least the command names are same/similar.. So your point stands, my point is more on the Aktually side.
web?