That was my deleted comment, but then I realized the article specifies they are Rome CPUs (Zen 2), while the 4000 series of EPYCs is based on Zen 4
Markaos
Nobody's saying that Google won't give them the code, though. Nothing is moving to closed source, Google just isn't going to be showing the current work-in-progress code for the next release to the public.
How so? I doubt many ROMs are based on code that isn't part of an Android release. Surely GrapheneOS devs can just use the Android 16 branch once it's released to make an Android 16 version of GrapheneOS.
Not in the CPU/modem department, that's a first
I don't think overheating would cause random corruptions (it should throttle down when overheating, and then shut down if the temperature gets too high even when throttled, but there should never be an incorrect result of any computation), and surely the RAM will run at the standard 2133 speed on default settings - OP says they reset the BIOS settings to default between CPU swaps.
A simple rm -rf says hello
Idk, seems like it's sticking out of the back and isn't symmetrical like the camera bar, so it might wobble or lay uneven on a table. That's way more obnoxious to me.
Google Maps is US-based whether you use it in the US or anywhere else
Sure, but I don't see how any of that disproves the current "M$ supremacy" for "normies" - the fact is that people who couldn't care less about how their computers work will have a much easier time using Windows (and probably macOS) than any Linux distro. You don't have to worry that some software won't be available to you because of your choice of the OS, and if you ever have a problem it's easy to find help.
I haven't used Windows in a decade on my personal computers, but as long as these two things hold true, it will always be my recommended OS for people who simply don't care - I'm not going to spend my time doing free IT support for everyone I know and then get blamed everytime something doesn't work.
Annoying warning keeps showing up at boot -> bring the PC to the nearest computer-literate person, and they'll fix it. Good luck doing the same if you use Linux.
xfwm is XFCE's window manager, and it's eating almost 30% of the total system memory, so that's the prime suspect (I'm not exactly sure how much it interacts with other apps, so it's possible something else is forcing xfwm to use all that memory, but that is IMHO unlikely).
An ugly "fix" is to log out and log back in (yes, not much better than just rebooting), or you could try to somehow restart xfwm - running
xfvm --replace
in terminal might work.Edit: there's an issue on the Manjaro forums that might be related: https://forum.manjaro.org/t/xfwm4-memory-leak-since-4-20/173910/7