I must have missed that negative sentiment entirely. I played all three and had no complaints. Did some searching, and apparently a lot of the gripes were related to levels being cut down in size / broken down into pieces to allow for a console release (strict memory requirements). Also I think they changed engines for the 3rd game, or at least a lot of people complain that movement and controls were worse in DS. I guess ignorance is bliss, cause I enjoyed them all.
Do you mean Thief: Deadly Shadows? That was the 3rd game in the series, and from what I understand it was pretty well received. The orphanage level alone is so highly regarded that it has its own Wikipedia page.
Now the 2014 reboot, just titled Thief, that was so poorly received the it basically killed the series. It might have been a decent game, but it was not a good Thief game.
Be lucky if we get out of this with only a recession. The slogan might as well have been Make America Great Depression Again.
Canadians have two moods. The first is “I’m sorry”, the second is “You’ll be sorry.”
Second mood activated.
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).
Anything that pushes the CPUs significantly can cause instability in affected parts. I think there are at least two separate issues Intel is facing:
Intel’s messaging around this problem has been very slanted towards talking as little as possible about the oxidation issue. Their initial Intel community post was very carefully worded to make it sound like voltage irregularity was the root cause, but careful reading of their statement reveals that it could be interpreted as only saying that instability is a root cause. They buried the admission that there is an oxidation issue in a Reddit comment, of all things. All they’ve said about oxidation is that the issue was resolved at the chip fab some time in 2023, and they’ve claimed it only affected 13th gen parts. There’s no word on which parts number, date ranges, processor code ranges etc. are affected. It seems pretty clear that they wanted the press talking about the microcode update and not the chips that will have the be RMA’d.
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.
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.