That falls under being ignored. Most people will only realise it’s a big deal if enough noise is made about it. Sony would maybe lose 10% sales from people quietly quitting, but still profit from the decision long-term. Right now the news article was only written, and we’re only talking talking about it, because enough people made a fuss. That’s how protests work; they’re not convenient or polite.

I don’t buy their games or consoles, personally. But I also don’t call Sony to complain, so I’m very much an outsider’s perspective on this.

I always thought this stance to be interesting, because it reminds me of soldiers in a conflict. The arguments are that the enemy rank and file are just doing their jobs, they have a family, the actual evil bigwig is out of reach, etc.

But also, are you just going to do nothing and let them steamroll you? They’re choosing to continue to work at that business, and are the only “frontline” that you can interact with. The fact that the business made a policy specifically addressing this common complaint, means it actually reached the ears of someone in power.

I’m not encouraging violence or anything of course. But, by design, there’s nobody else to voice your displeasure to. The only other option is to quietly accept their changes and be ignored.

If they didn’t want angry people calling, maybe they shouldn’t make terrible decisions?

Note: The images in this piece are dithered to reduce bandwidth

Wow, someone else who still does this! 15KB PNG images, in 2026!

TL;DR they configured uBlock to block almost everything, which breaks most websites, then only allowed the bare minimum to get things working again

Oh yeah that thing that makes my eyes bleed. I always turn off such “render resolution” BS in settings. Full scale native please.

What’s the upscaling with A.I. “before” that you’re talking about?

What do you say after running them over?

Willis makes clear that crunching was not mandated by id Software, but says that the amount of work they needed to do, combined with the timeframe the team was given to do it in, made the implication clear.

“You get loaded up with 60 hours of work in a week, and what do you do?” he says. “It’s almost this thing like, at the level of quality that the players expect and that you expect from yourself, it’s kind of like almost pseudo-induced crunch.”

Sounds like they had high personal standards, loyalty to the company, and were emotionally invested in the quality of what they’re working on. Big mistake in 2026.

Willis was one of the many id Software devs laid off as part of Microsoft’s massive cuts, in which it slashed 1,600 jobs (with another 1,600 being cut over the next fiscal year) and numerous studios like Compulsion Games and Double Fine were cut loose from Xbox Game Studios. Apparently, the Revelations team learned about the layoffs the day before the expansion was due to launch.

“You spend so much of your energy and hours of your life, and sacrifice a bunch of things to get something out of the door, and then they lay you off,” Willis said. “It’s such a wild feeling.”

The article goes into this.

Looking at the basic performance charts Nvidia has provided us so far, the ultra-high frame rate figures are based on 6x Multi Frame Generation. So, while the little RTX 5060 can churn out a 258 fps result in NBA 2K27 at 1080p Ultra settings with ray tracing and DLSS 5 enabled, the game underneath will actually be running at around 43 fps.

258 / 43 = 6

I haven’t looked at the raw numbers, but if the A.I. is reducing performance by 60%, you can do some basic math and estimate that your game would have 110FPS normally. So the A.I. technically comes out ahead by a lot of frames. But, are those frames actually valuable? 60fps is enough for me personality, and 120fps is more than enough for almost everybody, so anything more than 120 is basically fluff.

Also I don’t really want to play a game where 5/6 of frames are “fake”. Imagine just walking along in Elden Ring and you glitch through a wall, but the wall never existed, it was hallucinated by the A.I. based on surrounding geometry, and then you get hit by a random fireball the A.I. accidentally left out. I would be pissed. I can’t even imagine all the strange visual artefacts and glitches the A.I. would introduce. Like your character gaining and losing fingers in The Sims multiple times per second.

By that I mean you have to be careful which libraries you use. There’s a good chance that a System.* or random NuGet package will either completely fail to run on Linux, or be horribly buggy if you force it to work via build flags. In fact, they’ve completely removed the build flag in .NET 7+, System.Drawing.EnableUnixSupport. It used to be supported via libgdiplus.

I would expect .Net to be fully compatible with Linux out of the box. Especially system libraries. You can’t say that you support cross-compatibility, and then deprecate cross-compatibility of system libraries; that’s just insane.

I don’t remember the exact details because it’s been several years, but it was far more than just System.Drawing.Common that broke on Linux after updating to .Net 6. Some breaking changes were undocumented, only appearing later in GitHub issues. Some were buried in sub pages or individual library documentation.

In the patch notes they even had the gall the claim that our business use case doesn’t statistically exist, and we can just drop in replace SkiaSharp; which was absolutely not the case. It was an unmitigated fucking disaster, even accounting for rolling back to .Net 3.1 for a few months while we sort it out and wait for critical 3rd party libraries to accommodate the change. Before anyone says it, yes we actually paid handsomely for our critical third party libraries; we didn’t mooch off open source and whinge about it. Even so, it never really worked right after that change. A hundred small things, like differences in how SkiaSharp draws differently and handles edge cases. In an enterprise application, it was a big problem.

More reading: https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only

Firefox does only exist because Google pays for it. Google is Mozilla’s single greatest financial contributor. They’re essentially keeping a competitor on life support to avoid breaching antitrust laws. Essentially, the argument is that as long as Firefox exists, Google isn’t a monopoly.

However, at any time, Google could simply stop paying, and Firefox would quickly die. Laws change.

Yeah… I didn’t want to include 430MB of bloat in my bundle to each end user though for one feature, so I did it the hard way instead: Manually editing document files using XPATH. Maybe I’m too old school, if everyone’s shipping 1GB+ apps like it’s nothing nowadays.

Looks like it’s some kind of dependency… seems very odd though, why is this included? Are they using it to handle .docx, .xlsx, etc files? I remember being tempted to do that once years ago when I ran into one of those Really Hard Problems that would take weeks to solve. I spent the weeks instead

The duality of Lem

Ideally, yes; but cross-platform drawing libraries are like unicorns nowadays. SkiaSharp would probably work, but it functions completely differently and would require a rewrite of the entire program, which is a big ask.

DDoS (Distributed Doubt of Source)

25% inaccuracy is crazy. Might as well use one of those online tools to guess it

People trading their Stablecoin for Bitcoin

Latest version of Paint.Net is 5.1.12. Pinta got forked from 3.36. Would be cool if Pinta could just pull down 2 major versions’ worth of features. Instead, Paint.Net’s author resorted to vibe coding 180k unsupervised lines of code as a dodgy semi functional compatibility layer