I am not savvy in hardware space, but I'm speculating it can, for some reason, affect agressive trottling behavior of your CPU when it peaks. This causes evaiding correct evaluation of set conditions for said trottling that usually surprises these games enough to crash when their load becomes too high to handle. CPU doesn't turn into potato to save itself, thus games don't find themselves in the situation when it downsizes resources ready to use.
"In his hand" does some heavy lifting there. I've seen victorian corpse photoes more convincing than that, except maybe for open eyes. And that's the best they could do with his barely animated body?
Commodore is dead. Was dead for some 50+ years. If you want to revitalize said brand, you don't ride it like a horse (that is dead) but make something of value. Android flipphone with preinstalled meta software that blocks you from installing and using other apps is just crude.
We'd have extra PCIe slots on premium motherboards so every type of cores can be implemeted separately, e.g. CPU and NPU, CUDA and Turing\RTX. Shared memory would become a standard.
I don't think a lot of people decide so consciously as nearly no one installs their OS themselves, but yesterday marked the first time I installed W11 from the scratch on a premium laptop. Official enterprise image, last updates, it's Intel core 7 + 5060 + 32GB ddr5, and as I install stuff I can't launch start menu, it's just does not appear after clicking. Every other browser, installer or program responses as usual, but you just can't press Win and access notepad or whatever. How did they fuck that up so bad? On some dying w10 PCs with a faulty ssd I have the Start menu working weird, but on a fresh machine my client got from the store it's fucking bonkers.
You won't do this on corporate machines, but converting a Win install into an IoT release and generating a key for it is like a couple of clicks and a reboot.
But, but - the way massgrave is still accessible and not fought against makes you think Microsoft wants the fluctuating users to keep on using their products and ecosystem even if they don't pay the initial sticker price.
So if it's at least slightly feasible for your workflow, it's always better to switch and leave M$ behind.
P.S. I can be wrong, but IoT right now doesn't shield oneself from installing copilot and other garbage, making this edition not better than others, you still need to debloat it.
If not for you and the site's newsletter, I couldn't have got a handheld myself and could completely missed a lot of older gems I now slowly explore with joy. Keep it up! Niche Lemmy communities adore small and honest news sites covering what we are into, going out of their way to post it there and communicating with us directly. It's still work, but it looks you too enjoy it, and that's sweet. I hope to keep reading ya <3
With F-Droid apps - as long as they are privacy-friendly and completely localized, they are way safer than if social media app that handles credentials and always calls home becomes unmaintaned for like a week. They just don't take risks usual apps do and don't ask every permission on Earth. So, by design, even less maintained ones serving just one function and not using too much external libs are kinda ok. The danger arise proportionally to their web usage, and these apps usually see more frequent updates and traction.
Not really, I don't have money for a separate gaming console, and if I had, I'd probably still invest in my work machine. I want mass adoption for it become a reference in optimization for Linux systems but I myself can't chip in - I think that contradiction is shared by many.
Also, Linux Mint forums, Ubuntu forums and other close distros' forums - for questions that are likely to have been answered before. I prefer reading the thread myself rather than getting a summary, for it's a part of the fun - knowing there are lively communities and watching users suggest different approaches, good or bad, arguing, mentioning other topics that can come up later. It's not a systemic knowledge, rather case-by-case one, but it can be a path to some wider understanding of the OS.
We won't hear about it though.