Hardcore gamers tend to play competitive multiplayer games which today predominantly rely on anti-cheat detection with an in-kernel component. When these fail to run (because Linux is not supported) or when they detect you are trying to run it from a Windows VM with some form of GPU passthrough, the player account gets banned.

Nvidia will gobble up the CPU market as a function of the transition to AI. Intel is a has-been that's kept on life support for when Taiwan gets invaded before TSMC is ramped up sufficiently outside of Taiwan.

exactly - satellite communications intercept is not the big story here... if the Russians care to make a big effort to intercept they likely know that at least some of the sensitive data isn't sufficiently well encrypted that it becomes interesting to capture.

I never said it would - just that they do have non-volatile storage

The every-app-has-its-own-auto-update agent and infrastructure on Windows is a disaster in the making. It's not like we had enough warnings about thid in the past. For a long time, Microsoft was gatekeeping their update infrastructure by limiting their Store to UWP apps - now that they have come back on that decision, is there any reason not to depend on the update logic and infrastructure provided by Microsoft? On Linux I believe the equivalent risk more or less is adding third party repositories where the signing key isn't properly secured and segregated from the repository infrastructure.

Windows 10 Mobile basically was Windows 10 stripped from the legacy APIs - UWP apps ran fine. Of course most people use windows because it runs their legacy apps well, not because it can run UWP apps from an app store no developer cares about.

wouldn't the upgradeable firmware reside in non-volatile storage?

RADIUS using MSCHAPv2 authentication is the number one use case of NTLMv1 in the IT infrastructure of organizations. While it's very doable (and strongly recommended) to switch to X.509-based auth for wireless auth, typically username/password auth remains in use to administrate switches, routers and other physical network devices. Microsoft even excludes MSCHAPv2 for RADIUS from the NTLMv1 depracation timeline and MS NPS has a registry setting to allow keep using NTLMv1 even when it has been 'disabled' on the domain controller.

The post title contains: "Japan Votes to Restart Fukushima Nuclear Plant" None of the three linked articles in the post body talk about restarting the Fukishima nuclear plant. So what is this? sloppy editor, hallucinating LLM, both, other?

SailfishOS runs on the standard Android kernel, so it should be easy to port Android to the phone. The whole Android/libhybris approach coincidentally also the reason I'm not interested in this phone, and why I am of the opinion that GrapheneOS is the wrong approach unless if you ONLY care about cutting out Google from your personal data. What about all others that still can have access?

you can still rent computer resources that are 5-7 years old on AWS/Azure/etc. Why write off hardware when there are still willimg customers paying for them? It's not competitive compared to modern compute in terms of perf/watt (and thus perf/$), but some customers don't want to (re)valide proper functioning on a different platform.

what use is a secure OS if you cannot trust the unauditable binary blobs for the wifi, bluetooth and 4g/5g radio, nor can you trust most telcos who can run SIM apps with very low level access to the baseband without your knowledge or consent?

And if you actually had read wikipedia you would quickly find out that he's a technocrat and independant.

Intel has been consistently failing at Ai as well as almost everything else, so I don't see how that's going to be a hedge for an AI bubble pop. The only things Intel would be a good hedge for are success and a CCP takeover of Taiwan (admittedly this may have some value as the chances for this are likely far underappreciated in the market).

if the foundry splits off today, I would expect a GlobalFoundries result, with arrested development of new node sizes, as there isn't enough money to finance it. Keeping design and fabbing in one entity may at least force transfer of income from the design part to finance the new node sizes.