That’s my feelings after seeing Expedition 33 on UE5.

The game was absolutely phenomenal, but there is ABSOLUTELY no reason that that game should’ve forced me to upgrade my graphics card just to throw extraneous particle effect bullshit over every location that can’t even be turned off. It’s beyond ridiculous.

Do you want a thriving emulation scene?

Because that’s how you get a thriving emulation scene.

Because they all died, and then again on the corpse run.

Any company making games where they’re pushing graphics into top graphics card territory for no good gameplay reason can go straight to hell in 2026.

Yeah. I’ve only been a veteran of the process for 20 years - I don’t know a thing about what I’m talking about.

“non-breaking” is a meaningless distinction. What you’re REFERRING to is a “cosmetic” bug, and “cosmetic”, depending on the software and the shop, does NOT mean “acceptable for release”, and FURTHERMORE, this is not a new bug that’s been filed as low priority or will-not-fix, but a REGRESSION because it DID work in the past, which means it’s DOUBLE damning.

I’m not interested in waving around credentials about who knows more about software development - if you work in a shop that doesn’t care about quality, that’s between you and the shop. But if you want to claim that someone at Microsoft said “Yeah, it doesn’t correctly reflect the filename, a critical check to ensure users don’t accidentally delete the wrong file, which is something that’s worked for 30 years” and then signed off on that, instead of the MUCH more likely explanation that NOBODY is looking at ANY of this crap with the detail they should be, I’m afraid I’m going to have to laugh.

To give you an idea, in the XBox division, a division of Microsoft, this would be considered a compliance failure that prevents a game from going gold for launch on the platform, and if caught would cost the developer thousands and weeks to fix before the game could go live because it would necessitate starting the final step of the certification process over again.

But no - the same company would claim it’s totally acceptable for the operating system that runs bank software because it’s “non-breaking”.

Linux doesn’t charge hundreds of dollars per license to fund the development, rake in billions in profit, and then funnel that money into stock dividends instead of a proper quality assurance team.

It isn’t the details or severity of the break that matters.

It’s that the quality control process is SUPPOSED to catch that, and whatever sorry excuse for a process they’re using now ALLOWED a break that was obvious, visible, and repeatable, inside a critical, core function of the operating system, to make it to the end users, something that should trigger as an immediate, flashing warning light. That means the entire quality control process at the very least is SEVERELY compromised and unreliable, and there could very easily be MUCH more severe vulnerabilities and bugs hiding underneath that AREN’T immediately visible. To anyone who has done any professional development for non-disposable code bases, this isn’t a whisper of a problem - it’s an air horn.

How’s that attempt to get back onto consumers’ good side again going for you, AMD?

No good. LinkedIn is still up.

Putting it on the dispenser is too much work. Just put it on top and spin a few squares off with your finger in the roll when you need it.

They’ve been practicing for a long time

Yes, but let’s be honest…

If not for Star Wars his legacy would much more prominently feature brown face that has not aged nearly as well.

No, seriously though.

The hilariously low joke amount from the movie is BARELY less than the actual settlement amount.

It’s pretty easy to not get caught surveiling customers.

All you have to do is… Not surveil customers.

Get one now… Their prices are set to quadruple because of data center contracts.

Did technical debt write this?

That there’s a question over who owns the things you bought is already beyond dystopian nightmare.

Watched you price gouge right there with Nvidia during the crypto nightmare days.

Fuck off. The north remembers.

deleted by creator