Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

tomshardware.com

Post reply on HN
Print view View original

361–370 of 415 posts

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

#361

Post by devinprater »

Dylan16807 wrote: post #156
matthew-wegner wrote: post #82

Earlier quoted context omitted.

Hold up. It's been ~14 years since Apple shipped machines with 2GB of memory as base their base model. macOS (and iOS) have incredibly good screen reader support, as well as all of the things you're complaining about in your original comment at the top of this thread. Clearly those things are absolutely gobbling memory, and yet you don't seem to connect the dots that they're directly contributing to high memory requi…

> I'm not sure you're in an position to rail against high-memory bloat in computing today. Nobody is a hypocrite for buying X gigabytes of ram but also wanting the naked operating system to use a much smaller amount, or wanting single programs to use a much smaller amount. > macOS (and iOS) have incredibly good screen reader support, as well as all of the things you're complaining about in your original comment at th…

Mainly the TTS engine being ready for input, stuff like that. Of course you could go to Linux where you have to enable assistive technologies support before the whole desktop understands that they should work with screen readers. I'm guessing that there is where accessibility does take up RAM and resources.

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

#362

Post by rejectfinite »

worble wrote: post #149

It really staggers me the lengths some people will go to try and preserve something that is actively against them, when there are alternatives right there. I'm not saying Linux is for everyone, but the kind of people creating and running these scripts really should have no issue daily driving Ubuntu or even Arch. Or if they desperately need photoshop or whatever, get a mac. It's like watching people constantly go bac…

This is not for regular Windows 11 useage... This removes WinSXS so cannot be upgraded, apps wont work etc etc

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

#363

Post by 10xDev »

npteljes wrote: post #344
grumpywndw_user wrote: post #105

Windows 10 pushed me to become a permanent macOS and linux resident. I don't know what went wrong but Windows 2000 was perfect, with 7 being almost as good.

What's wrong is not to realize that these are businesses, not endeavors to create the perfect operating system. Your incentives are just not aligned with Microsoft's, simple as that.

Good thing you can be both a business and still care about user experience.

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

#364

Post by DavideNL »

TacticalCoder wrote: post #162
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…

> Let’s pause for a bit and dwell on the absurd amount of RAM it takes to run it even after this exercise. I agree and I find the apologists to be completely wrong. I run a modern system: 38" screen, 2 Gbit/s fiber to the home. I'm not "stuck in the past" with a 17" screen or something. The thing flies. It's screaming fast as it should be. But I run a lean Debian Linux system, with a minimal window manager. It's defi…

What would you say is the best Desktop environment for Debian for an average user (not Development), modern PC, and some gaming (nvidia 3080Ti)?

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

#365

Post by xvilka »

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…

Using Web technologies for places where they don't belong killed the performance.

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

#368

Post by NikolaNovak »

JoeAltmaier wrote: post #23
Someone1234 wrote: post #4

This removes WinSxS. That's fine for embedded, since you'd just package the DLLs you need with any executables you want to run, but trying to run this as a general purpose OS is a fools' errand. Calling WinSxS "bloat" when that "bloat" is allowing 30+ years of backwards compatibility (and a lot of stuff will break) is creative by the article's author for sure. Nothing wrong with Tiny11 though, if you know what it is…

Um. Where else do you need it to run in 2GB but embedded? I think the article is informative, fair and correct.

I have a media pc running windows 10 with 2gb ram. It's run great with media player classic, Netflix, and even steam installed. I certainly would not assume "debloated" means "completely crippled"

I think that's the point - some people have assumption that 2g is meaningless whereas others see it as HUUUGE amounts of memory. Never mind historically, let us consider what a modern phone can do with 2gb ram.

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

#369

Post by smileybarry »

Dalewyn wrote: post #207
Ar-Curunir wrote: post #102

Earlier quoted context omitted.

Because integration into the desktop is better as an Electron app. Eg sound and video calls, keyboard shortcuts, not having to worry about finding your Discord/Slack/whatever tab

I would't say Electron is better desktop integration. Discord for example is literally just a chrome-less Chrome; the zoom in/out hotkeys in Chrome still work in it. This is also not mentioning how no Electron program ever visually adheres to the desktop environment it's running in.

> Discord for example is literally just a chrome-less Chrome; the zoom in/out hotkeys in Chrome still work in it.

No, it also includes:

* Voice (and text chat) overlay for games (DLL)

* Game integration via lobby & rich presence APIs

* Krisp noise cancellation (requires a DLL as well)

* (Better) screenshare (Chrome has an API for window sharing now but Discord's is a bit more robust with several backends in case one fails)

* System-wide keybinds

* Scripting support via gaming accessory apps (Logitech G HUB, HyperX, etc.)

It also (anecdotally) works faster than the web client, in my experience.

Just because the zoom controls work (which is an accessibility feature) doesn't mean it's a barebones Chrome wrapper.

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

#370

Post by muyuu »

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…

early expectations on code interfacing and re-usability failed catastrophically

in my previous job rather than give people root access to their laptops we had to do things like running a docker image that ran 7zip and we piped the I/O to/from it, and I'm not kidding we all did this and it was only bearable thanks to bash aliases and the fact that we had 16GBs of RAM

Post reply on HN