Live data from Hacker News

De-Bloated Windows 11 Build Runs on 2GB of RAM

tomshardware.com

301–310 of 415 posts

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#301
post #251

Earlier quoted context omitted.

So you would say programs today are equally efficient and more stable, just have more features?

In generally I would say far more stable and far more features. But this of course is in the metrics of how you measure. Windows 3.1 for example was a huge crashing piece of crap that was locking up all the damned time. MacOS at the time wasn't that much better. Now I can leave windows up for a month at a time between security reboots. Specialized Windows and Linux machines in server environments on a reduced patchin…

Did windows 3.1 even have memory separation? So a bad program could crash the whole system?

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#302
I feel like a new law needs to be named after this, maybe it already exists and I am just unaware of it, but 'basic computing functions and operating system requires expand to match the standard level of computing performance available"

It's crazy how things that were considered basic many years ago so run well within the performance we have in modern systems, yet the basic system has requirements much higher than it used too.

Teams is a massive example of this, is just text chat and video conferencing, stuff that was easily done 10 years or more ago, yet there are plenty of systems available today that run it like crap, let, alone imagining to run this on a ten year old system.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#303

Earlier quoted context omitted.

The idea that removing WinSxS saves space is generally misguided anyway. The vast majority of content there is actually the original file that was used to create a hard link at the destination. So obviously removing the file doesn’t really save any appreciable amount of space. The remaining content unique to WinSXS is either for cryptographic validation, app compat, or the driver stack.

Hmm, so how can you see the real size of winsxs?

Brute force?

Get the size of every “file” in the volume along with the file id of each and then subtract the size of any files with a matching file id that are in the WinSxS. Then sum the size of the remaining files that were from the WinSxS.

You can get the file id using https://learn.microsoft.com/en-us/windows/win32/api/winbase/... or fsutil, etc.

You could also probably execute “fsutil hardlink list” for every “file” in WinSxS and then ignore any that list more than one result and sum the size of the remainder.

There are of course more efficient ways to do this but those are some quick hacks.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#304
post #197

Earlier quoted context omitted.

It is still possible to have a snappy computer experience. Go Linux, use a very configurable distro (Arch, Gentoo, NixOS), choose a lightweight DE and app ecosystem and it will get you there for the most part. Browsers are still going to be the sticking point, but with agressive adblockers/noscript and hardware that's not terribly old (NVMe storage is priority 1), and you should be set. But of course, snappiness isn'…

I’m on debian and using xfce. The problem is the web browser. I’ve got 16 gb of ram and the browser is using most of them. I can literally see the swap space emptying when i have (as in “im forced to”) sacrifice my browsing session (xkill the browser) due to constant swap out to disk. And I’m using a pci gen 3 nvme disk, and already lowered swappiness. The problem is the web browser.

In my experience, changing swappiness makes everything worse and you end up back with the default value in the end.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#305
post #6

Let’s pause for a bit and dwell on the absurd amount of RAM it takes to run it even after this exercise. Anyone here remember when QNX shipped a demo in 2000 with a kernel, GUI, web browser and an email client on a single 3.5” floppy? The memory footprint was also a few megabytes. I’m not saying we should be staying within some miserly arbitrary constraints, but my goodness something that draws UI and manages process…

Well, other operating systems are still relatively decent at this. My main Linux install eats ~250 MiB of RAM after startup, and I've spent exactly zero amount of time on that, so it can be trimmed down further. That's on a system with 32 GiB of RAM — if you have less RAM, it will eat even less since page tables and various kernel buffers will be smaller. FreeBSD can be comfortably used on systems with 64 MiB of RAM…

Which distro? Last Linux distros I tried wasn't exactly lightweight RAM wise.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#306

Earlier quoted context omitted.

I don’t like the direction GUIs have gone either, and think the JavaScript-ization of everything has been pretty dumb. But it seems that bloat is doing well in the market. Users might not care about developer experience, but everything is a trade off: developer time is a cost, the cost of producing software is an input into how much it needs to cost. Users seem to want features delivered quickly, without much regard…

Users just don't have much say in the matter. Case in point: Discord and Slack are atrocious UX-wise. You're still forced to use them because, as with any walled-garden communication service, you aren't the one making this choice.

IM-ing programs seem more like the exception, rather than the rule.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#307
post #197

Earlier quoted context omitted.

It is still possible to have a snappy computer experience. Go Linux, use a very configurable distro (Arch, Gentoo, NixOS), choose a lightweight DE and app ecosystem and it will get you there for the most part. Browsers are still going to be the sticking point, but with agressive adblockers/noscript and hardware that's not terribly old (NVMe storage is priority 1), and you should be set. But of course, snappiness isn'…

I’m on debian and using xfce. The problem is the web browser. I’ve got 16 gb of ram and the browser is using most of them. I can literally see the swap space emptying when i have (as in “im forced to”) sacrifice my browsing session (xkill the browser) due to constant swap out to disk. And I’m using a pci gen 3 nvme disk, and already lowered swappiness. The problem is the web browser.

I have 32GB RAM and Firefox is currently using 2.5% of that. I use ublock, noscript and Auto Tab Discard.

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#309
post #31

Earlier quoted context omitted.

Hasn't it, though? HDR, fluid animations, monstrous resolutions, 3D everything, accessibility, fancy APIs for easier development allowing for more features, support for large amounts of devices, backwards compatibility, browsers are almost unrecognizable in featureset to the point they resemble an OS unto themselves, email clients have stayed mostly the same at least except for the part that they also ship a browser…

> HDR, fluid animations, monstrous resolutions That's the job of the GPU driver, mostly. > 3D everything That's the desktop compositor. Windows 7 already had one and ran on 1 GB of RAM. > accessibility Not everyone needs it, so it should be an optional installable component for those who do. > fancy APIs for easier development allowing for more features That still use win32 under the hood. Again, .net has existed for…

[deleted]

Re: De-Bloated Windows 11 Build Runs on 2GB of RAM

#310
post #217
post #33

Earlier quoted context omitted.

"De-bloated" implies that the stuff removed is "bloat", i.e. worthless. I wouldn't assume that a "de-bloated" install was any less suitable for general purpose computing tasks.

I'd consider that a poor assumption. If you try to use this to install a wide range of applications you run into one of two issues, you rebloat the system, or some things fail to run.

I think the core question is what is the definition of bloat.
Post reply on HN