De-Bloated Windows 11 Build Runs on 2GB of RAM
tomshardware.com
De-Bloated Windows 11 Build Runs on 2GB of RAM
1–10 of 415 posts
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#2Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#3Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#4Nothing wrong with Tiny11 though, if you know what it is good at and use it for that. Namely, "offline" Windows for some appliance-like usage (e.g. factory controls, display screens, et al) when Linux won't do for whatever reason and licensing Windows IoT isn't possible (small business/personal project/etc).
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#5Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#6Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#7Let’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…
https://en.m.wikipedia.org/wiki/GEOS_(8-bit_operating_system...
Obviously there were huge limitations but it shows what can be done. This fit on one 170K floppy and ran on a 1.44mhz 8 bit machine with 64K of RAM.
In the 1990s I ran both Linux and Windows on less than 64M of RAM with IDEs, web browsers, games, and more.
If I had to guess what were possible today I’d fall back on the fairly reliable 80/20 rule and posit that 20% of todays bloat is intrinsic to increases in capability and 80% is incidental complexity and waste.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#8Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#9Let’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…