https://m.youtube.com/watch?v=IwLSrNu1ppI

Or the 10 hour version, for true gnomecore madness: https://youtube.com/watch?v=iDNQYJUdxks

There is an option to pay for Extended Security Update (ESU) support for Windows 10. It’ll give you access to critical security and Windows Defender antivirus updates, but no fixes or updates to features. There are three ways to pay:

• “Free” if you’re syncing data to their cloud (pay by letting them datamine your data and settings)
• With Microsoft Reward points, which I believe are primarily earned by using Bing (pay by letting them datamine your searches)
• For $30 a year, at least for the first year, though I’ve read the price goes up each year as they want to drive everyone to Win11.

The program would conceivably allow you to kick the can down the road, possibly as far as Oct. 2028. Personally, I opted instead to switch to Linux months ago instead, and don’t regret my choice.

The vast majority of this increase is from people playing on Steam Decks

I believe this is incorrect. The Steam survey break down GPUs by description and the Deck’s GPU appears in the results as “AMD Vangogh”, which only accounts for 0.39% of respondents. That implies that the vast majority of survey respondents using Linux are actually on PC, not the Deck.

Some of my all-time favorites! I imagine there were precursors in terms of game design, but these were the first games I ever played where the enemy AI seemed actually intelligent. Like, guards would notice if you made noise, or if a torch had been extinguished. If they found the body of another guard they’d start searching for you. Pretty standard stuff these days, but that was a very fresh concept at release.

The studio behind Thief (Looking Glass) collaborated with Irrational Games on System Shock 2. Thief 1/2 and SS2 both used the Dark Engine, which leads me to my favourite piece of game dev lore/trivia. Because Thief was developed first, the game engine had code for sword parries. During SS2’s development they had persistent issues with that parry code activating when it shouldn’t. Testers would be trying to bean a psychic monkey with a pipe wrench and the monkey would parry with an invisible sword.

I did almost the exact same thing, on the same timeline! Installed Bazzite on a second NVMe sometime in the spring, and it’s been my daily driver for months now. For the first couple months I was swapping back and forth due to some graphics driver instability, but that’s because I got a 9070XT at launch and it took a bit for the Linux drivers to get to where they needed to be. That’s pretty much sorted now though, and I can’t remember the last time I booted into Windows.

Guess who just gained a 1TB drive to install more games?

I might use mine to try other distros. Bazzite has been great so far, but I’m not sure I’m sold on immutability and I might try a non-Fedora based distro.

Not the person you replied to, but I’m in agreement with them. I did tech hiring for some years for junior roles, and it was quite common to see applicants with a complete alphabet soup of certifications. More often than not, these cert-heavy applicants would show a complete lack of ability to apply that knowledge. For example they might have a network cert of some kind, yet were unable to competently answer a basic hypothetical like “what steps would you take to diagnose a network connection issue?” I suspect a lot of these applicants crammed for their many certifications, memorized known answers to typical questions, but never actually made any effort to put the knowledge to work. There’s nothing inherently wrong with certifications, but from past experience I’m always wary when I see a CV that’s heavy on certs but light on experience (which could be work experience or school or personal projects).

That’s just what happens to CEOs of publicly traded companies when they have a bad year. And Intel had a really bad year in 2024. I’m certainly hoping that their GPUs become serious competition for AMD and Nvidia, because consumers win when there’s robust competition. I don’t think Pat’s ousting had anything to do with GPUs though. The vast majority of Intel’s revenue comes from CPU sales and the news there was mostly bad in 2024. The Arrow Lake launch was mostly a flop, there were all sorts of revelations about overvolting and corrosion issues in Raptor Lake (13th and 14th gen Intel Core) CPUs, broadly speaking Intel is getting spanked by AMD in the enthusiast market and AMD has also just recently taken the lead in datacenter CPU sales. Intel maintains a strong lead in corporate desktop and laptop sales, but the overall trend for their CPU business is quite negative.

One of Intel’s historical strength was their vertical integration, they designed and manufactured the CPUs. However Intel lost the tech lead to TSMC quite a while ago. One of Pat’s big early announcements was “IDM 2.0” (“Integrated Device Manufacturing 2.0”), which was supposed to address those problems and beef up Intel’s ability to keep pace with TSMC. It suffered a lot of delays, and Intel had to outsource all Arrow Lake manufacturing to TSMC in an effort to keep pace with AMD. I’d argue that’s the main reason Pat got turfed. He took a big swing to get Intel’s integrated design and manufacturing strategy back on track, and for the most part did not succeed.

Being a private company has allowed Valve to take some really big swings. Steam Deck is paying off handsomely, but it came after the relative failure of the Steam Controller, Steam Link and Steam Machines. With their software business stable, they can allow themselves to take big risks on the hardware side, learn what does and doesn’t work, then try again. At a publically traded company, CEO Gabe Newell probably gets forced out long before they get to the Steam Deck.

Beware of reverse survivorship bias. We’d know relatively little about the smart deviants if they rarely get caught.

It’s likely CentOS 7.9, which was released in Nov. 2020 and shipped with kernel version 3.10.0-1160. It’s not completely ridiculous for a one year old POS systems to have a four year old OS. Design for those systems probably started a few years ago, when CentOS 7.9 was relatively recent. For an embedded system the bias would have been toward an established and mature OS, and CentOS 8.x was likely considered “too new” at the time they were speccing these systems. Remotely upgrading between major releases would not be advisable in an embedded system. The RHEL/CentOS in-place upgrade story is… not great. There was zero support for in-place upgrade until RHEL/CentOS 7, and it’s still considered “at your own risk” (source).