kasabali

I understand that and I still say games shouldn't have the ability to do this.

who died and made you the arbitrator of deciding the "main use case"

irresponsible of what? allowing people use the hardware they own as they wish?

DDR5 has always been twice as expensive as DDR4. But yeah when they were a lot cheaper maybe it didn't matter as much as it does now.

its manufactured on a smaller node so probably has more leeway for higher freq on all core loads.

I’d also be weary of single core scores,Geekbench is known to be favoring specialized instruction sets like AVX or encryption extensions more and more as the version number progresses. Though I don’t know if GB6 is also like this I wouldn’t be surprised it it was caused by it.

The problem with this is Microsoft foresaw it and pushed (bribed?) OOXML through ISO and now there's no standing on "forcing" an open standard without OOXML being one.

Sure, if you ignore PQ completely.

Not that libjpeg-turbo is pinnacle of quality but hardware encoders, seriously?

joke's on you, it has never worked for me.

IMO Aero parts looked phenomenal but older Win32 parts like toolbars etc. didn't fit and looked odd

> Based on rumours Samsung finally cracked the secret on removing creases…

That's every year since it's introduction

That's textbook FUD.

xdotool and wmctrl is what you need

It may be 20 less but still hundreds. I'll never understand the LTSC advocacy, it is still the same thing except they mopped up the most disgusting looking liquid seeping out to the floor but didn't touch the huge turd sitting in the middle.

> - 100% minimal designed for absolute performance coded ground up in rust

Rust didn't exist in 90s yet Windows' performance was pretty good speed, consumption or bloat-wise.

> https://schneegans.de/windows/unattend-generator made all those tools obsolete and useless for the most part, "debloating" after it's installed is always bad business.

Unattended is no "magic". Go ahead and inspect the xml file created by that utility, all the customization and debloating is practically same as running a script post install.

If you really want to debloat before it's installed you want this: https://ntlite.com/

Play services isn't an "app", it's a highly privileged system service that has access to everything and some more.

> You can create an account with no phone number during Android device setup.

Yeah now they have IMEI and all the other device specific info anyway they might as well forego the phone number

> For extra privacy, you can sign into the Play Store with a Google Account that isn't tied to anything else.

I dare you try creating a Google account that isn't tied to anything else.

Nowadays you can't even create an account in desktop browser without first having to scan a qr code from a mobile device first.

"For a device with 8 GB, an app can use no more than 2.25 GB in the foreground, 1.5 GB for user-perceived services, and 1.5 GB in the background"

These are still very generous limits I doubt that'll help at all

"... it's on a Mac ..."

Tells you everything you need to know about Windows in 2026.

Android is a heavy Rube Goldberg machine, it's amazing it even works at all.

That’s a ridiculously unbalanced system and I very much doubt it was the norm. Even the cheapest systems in early 00s that came with a Celeron and 128 MB RAM had something like a TNT card with 32MB ram, that’s if not a bottom of the barrel GF2 with 64

This isn’t true anymore beginning with DDR4 speeds.

Because it's a big fat lie

Still goddamn bloat. No amount of sharing will change that.

Cheapest local brand 15" CRTs could do 1280x1024 in early 2000s. because you weren't limited by the panel unlike LCDs.

You'd need better than perfect vision to be able to make use of it, though.

> ~300MB is perfectly acceptable if it works well, looks good and does what it should do.

No it isn't. It isn't a word process for gods sake. It has one literally one job and 300 MB is like an order of magnitude off for that. This mentalty is the slippery slope that led us to the situation in the OP today.

> It is clear from the article that what eats up so much RAM is not the weather app itself but the framework it runs on. There is a "Renderer", a "GPU Process",... eating most of it.

You say tomato we say tomahto

At the end of the day bloated app is a bloated app its consequences are the same.

> mpv --idle --force-window 160 MB

That's still a HUGE amount when you remember mplayer (which mpv was based on) ran on PCs that has had less RAM than that.

> Nautilus is probably pre-indexing directory structure so it doesn't have to read disk every single time you open your home folder. That's good

No it isn't good, and no it probably doesn't because it is kernel's job. I'd rather they don't do double caching, and it's actually worse if they do.