News for hackers. Stuff that matters.

A comment on De-Bloated Windows 11 Build Runs on 2GB of RAM. Parent comment

Re:De-Bloated Windows 11 Build Runs on 2GB of RAM by causality0 on Saturday February 04, 2023 @10:38AM (#34655230)
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.

Taking up a lot of space on your drives for data to maintain backwards compatibility makes sense. Why, when not being actively used, does it need to occupy gigabytes of RAM?

[ Parent | on HN ]
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM by Someone1234 on Saturday February 04, 2023 @10:41AM (#34655254)
> Why, when not being actively used, does it need to occupy gigabytes of RAM?

There's no need, which is why it doesn't.

[ Parent | on HN ]
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM by ninkendo on Saturday February 04, 2023 @11:43AM (#34655750)
Given that the premise of this discussion is how Tiny11 credits removing WinSXS as part of the reason they were able to free up the memory, it would appear the article (and OP) disagree.
[ Parent | on HN ]
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM by Dooflegna on Saturday February 04, 2023 @12:00PM (#34655924)
The article talks about memory savings and storage savings. Removing WinSXS is a storage savings play, not a memory savings play.

Here's the relevant quote:

> Moreover, removing the Windows Component Store (WinSxS), which is responsible for a fair degree of Tiny11’s compactness, means that installing new features or languages isn’t possible.

[ Parent | on HN ]
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM by ChuckNorris89 on Saturday February 04, 2023 @10:51AM (#34655327)
Caching frequently used apps for snappiness.
[ Parent | on HN ]