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

Post by alpaca128 » Sat, Feb 04, 2023, 5:27 PM UTC

api wrote: post #7

abraxas wrote: 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…

My favorite is Geos for the Commodore 64: 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…

Post by znpy » Sat, Feb 04, 2023, 5:33 PM UTC

mixedCase wrote: post #16

abraxas wrote: 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…

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…

Post by anthk » Sat, Feb 04, 2023, 5:37 PM UTC

pancrufty wrote: post #5

It’s a great exercise but this is akin to Alpine Linux: it works for some things but you wouldn’t use it as your daily driver

Post by cratermoon » Sat, Feb 04, 2023, 5:39 PM UTC

KronisLV wrote: post #69

dagmx wrote: post #49

Earlier quoted context omitted.

Accessibility is much more than just labels for a screen reader. Please stop trivializing anything that you don’t use directly, it’s a common thread between all your comments, and it’s a disservice to both the points you’re trying to make and the people who actually use those things . Accessibility includes interaction design, zoom ability, audio commands, action link ups, alternate rendering modes, alternate motion…

> Accessibility includes interaction design, zoom ability, audio commands, action link ups, alternate rendering modes, alternate motion modes, hooks for assistive devices to interact with the system. It goes far deeper into the system than just labels for a screen reader. I wonder where the current status quo lies in regards to both desktop computing and web applications/sites. Which OSes and which GUI frameworks for…

Post by abraxas » Sat, Feb 04, 2023, 5:44 PM UTC

djur wrote: post #36

grishka wrote: post #31

Earlier quoted context omitted.

> 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…

> Not everyone needs [accessibility], so it should be an additional installable component for those who do. The UI has to be designed from the ground up to support accessibility.