Honestly, I just gave up after I bought my last computer, installed POP OS and installed Steam and have so far been able to play all my games without a single issue, except The Witcher 3 which only required a configuration change and I was golden. I will use Windows only on work machines but on personal machines its Linux for me from now on.
De-Bloated Windows 11 Build Runs on 2GB of RAM
211–220 of 415 posts
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#212Earlier 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…
I wish I could upvote you a thousand times. This this and this a 100%. It's sad today's "developers" will look at this and just say "ok, boomer"...
Being someone from back in those days they'll tell you to load up that software that fits in some small amount of memory. You'll find most of it is crash filled hot garbage missing the features you need. And the moment you wanted to add new features you'd start importing libraries bloating the size of the application.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#213Let’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 go to on this was I remember running Debian on a Pentium 166 with 32MB of RAM back in 98/99. It would boot to the desktop only using 6MB. It wasn't flash but it could handle the basics. Heck Windows XP would boot to Desktop using a little under 70MB.
But this isn't just Windows, currently I am on Kubuntu 22.04 and it is using about 1.5GB to get to the Desktop! Yes it is very smooth and flash but it seems like a bit much to do this.
This is why I am interesting in projects like Haiku and Serenity OS, they may bring some sanity back into these things.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#214Honestly, I just gave up after I bought my last computer, installed POP OS and installed Steam and have so far been able to play all my games without a single issue, except The Witcher 3 which only required a configuration change and I was golden. I will use Windows only on work machines but on personal machines its Linux for me from now on.
youre cursed like the rest of us and you will use windows only on work machines AND GAME MACHINES and linux for personal
EDIT: spelling and attempted to adjust elegance
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#215Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#216Earlier 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…
> > browsers are almost unrecognizable in featureset to the point they resemble an OS unto themselves
> No one asked for this. My personal opinion is that everything app-like about browsers needs to be undone, yesterday, and they should again become the hypertext document viewers they were meant to be. Even JS is too much, but I guess it does have to stay.
People did ask for this, because it made them a lot of money.
You should recognize your opinion is a minority one outside of tech (and possibly, there too).
To wit, virtually no one is jumping to Gopher or Gemini.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#217Earlier quoted context omitted.
Um. Where else do you need it to run in 2GB but embedded? I think the article is informative, fair and correct.
"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.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#218Earlier 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…
>That's the desktop compositor. Windows 7 already had one and ran on 1 GB of RAM. Compiz ran fine with a 128MB GPU and 512MB of RAM.
I think I first saw it running on a Geforce with 64MB of RAM. Even then it was smooth as butter.
Now that I think about it, Mac OSX was doing GPU compositing back in 2000/2001 and those machine usually only had about 16MB of VRAM. I remember it running fairly well on a 2005 MacMini G4 with 32MB of VRAM.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#219Earlier quoted context omitted.
> 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.
[flagged]
Keyboard shortcuts and navigation are accessibility.
Dark/light mode is accessibility.
Reduced animations/not animating tiles, etc. is accessibility.
Being able to scale/zoom in on fonts and images is accessibility.
Ensuring your automated GUI tests can interrogate the application/page's structure and state is accessibility.
Not reloading the entire page to render search results that would lose searh filter selection and/or current keyboard focus is accessibility.
etc.
Re: De-Bloated Windows 11 Build Runs on 2GB of RAM
#220Earlier quoted context omitted.
What debloat script did you use, and how did you decide which one to use? My experience is that there is a lot of them out there, and it's impossible to tell which ones actually do something that results in an observable difference, and what the potential drawbacks are of the things being changed. A lot of the time I feel like you end up with having to do a lot of research for a very minor practical effect.
I used this one https://github.com/Sycnex/Windows10Debloater and yeah I had to heavily customize it and then I did need to re-enable something afterwords which I found on the github. Basically what I did was I started with the default and then unchecked (or checked? I don't remember what the UI called for now) anything related to Xbox and the Store and I didnt have any issues. I also did a comparison before and after…
I used that one as well on the machine I use exclusively to log into work through web browser. The change was incredible, battery life shot up from 2.5-3 hours up to 6 plus.