Exactly. WP have had years to sort this shit out, but they were too afraid of cannibalising their existing base. I genuinely hope this gains support from plugin authors and wipes WP out.

Nope, it's 100% the WebView2 component. Video adds a bit but not much.

Microsoft Teams is an egregious one. It used to be Electron-based and nominally used gigabytes of RAM, was horrifically slow, etc. So, they switched to their own WebView2 (i.e. embedded Edge instance) and now it typically uses hundreds of megabytes instead...

...but that's still hundreds of megabytes to display a chat window with some text and a few images. Yes, the kind of thing you could do in literally a handful of megabytes with native code. Instead, we have an entire browser engine rendering this stuff and eating RAM like it costs nothing.

Just by scrolling up in a Teams chat window I got it to go from around 600MB to 2000MB RAM use in under 60 seconds. Bear in mind that all it's doing is fetching and drawing images and text. That's the power of the web, baby.

Nah, I think MS consider .NET code to be "native". The CIL gets JITted (and usually cached) into machine code at (or sometimes before) runtime. .NET apps don't have the massive overhead of an Electron app, for example. WinUI is native and not the worst UI toolkit MS have ever released - aesthetics aside.

Node.js and NW.js are only really awful because people realised if you just bundled them with a Chromium engine you could create multiplatform "desktop apps", and voila, you've invented Electron; 10x more resource usage and 10x less performance compared to a native app because web browsers are ridiculous behemoths these days.

Pretty sure Sam Altman has that exact phrase tattooed somewhere intimate.

Yep, and if the system isn't built to shield those doing the "verifying" then there should be a clear audit log proving exactly that.

Want to bet that log is incomplete and/or missing? I can't read the paywalled article to find out.

The AI does that without any prompting. That is the problem.

My (jokey) point was that the actual data between the samples doesn't exist in the file; you're always hearing an approximation. An infinitesimally close approximation at high enough sample rates, but still an approximation.

Your name checks out, tho. :D

Uh, those screenshots were clearly taken several seconds apart. The background characters had just... moved in the scene. That wasn't DLSS deleting entire characters.

Hey, wait until you hear about linear interpolation in animation. Did you know some of the animation frames in game models don't exist? The data between keyframes is being made up! The models are moving by themselves. Spooky.

And audio! Did you know we only sample audio at around 48Khz? It's not even a continuous analogue wave! The audio in the gaps between the samples every 0.000020833333333333 seconds is being made up! That's not even real data!

Oh, and don't get me started on pixel latency on LCD displays. Did you know that the image you see is actually different from what your graphics card puts out? Those blurred pixels in the few milliseconds between each frame don't exist! They're being made up by the LCD panel!

It's all a conspiracy, I tells ya. Big Tweening is out to get us.

Not if you look at how Musi actually worked.

I'd agree if Musi were offering a different product, and not just repackaging an existing product owned by someone else while collecting fees.

Indeed. From what I can gather from 5 mins of searching, this Musi app was essentially a YouTube wrapper. It streamed music directly from YouTube without actually showing any YouTube assets or - more importantly - ads.

Calling themselves a streaming service seems like a stretch. What they did was stream YouTube's content and place their own ads over it. Apparently they made over $100M in one year doing this.

You can argue about the actual legality of what they were doing, but it definitely breached YouTube's TOS. Obviously, so do most ad-blockers, but this wasn't on an individual level, this was enabling millions of people to avoid YouTube ad impressions and eat YouTube's bandwidth while siphoning the ad revenue from those views/listens.

Perhaps YouTube discovered there was no simple way to prevent what Musi was doing through technical means, so instead YouTube complained to Apple. Apple said "yeah, fair enough" and took the app down. Musi sued Apple and lost because Apple's TOS says "we can remove your app whenever we like for any or no reason". Musi's gravy train is permanently derailed.

I'm finding it hard to get worked up about this, tbh. Boils down to "whose flavour of greed do you prefer?"

You're completely missing the point. What's the alternative here? Get someone to produce actual SuperFX chips in 2026? Good luck with that.

This is not remotely equal to what you're talking about. This is using an off-the-shelf part to replicate the functionality of a component that is no longer manufactured. It is functionally identical to putting an actual SuperFX chip in the cartridge, only - you know - actually feasible.

It seems unthinkable that this won't be hacked to run Asahi.