but complexity merchants make them weight as much as the sun.
Windows 11's built-in Weather app wastes more than 1 GB of RAM
561–570 of 597 posts
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#562Earlier quoted context omitted.
2 years ago I stated that we should stop worrying about software consuming a lot of ram. I had just built my pc with 128gb of ddr5 ram spending less than an average android phone (I think like $300). I would like to retract that statement. Thanks.
this post was sponsored by SK Hynix
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#563Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#564Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#565Earlier quoted context omitted.
> It is clear from the article that what eats up so much RAM is not the weather app itself but the framework it runs on. There is a "Renderer", a "GPU Process",... eating most of it. You say tomato we say tomahto At the end of the day bloated app is a bloated app its consequences are the same.
10 apss using 100mb each plus 600mb shared use less ram than 10 apps using 200mb each.
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#566Earlier quoted context omitted.
2 years ago I stated that we should stop worrying about software consuming a lot of ram. I had just built my pc with 128gb of ddr5 ram spending less than an average android phone (I think like $300). I would like to retract that statement. Thanks.
On the flip side, high 5 for getting 128gb of RAM at exactly the right time!
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#567Earlier quoted context omitted.
Pictures and frame buffers. If you're running fullscreen at 4k, you're probably gonna take two roughly 3840x2160x3 byte frame buffers for the window. Your designers want a background image which moves as you scroll in some parallax style; that's over 3840x2160x3 bytes more for the pixel buffer backing the image layer. And let's say roughly 50% of your screen is text with subpixel (aka full color) anti aliasing; that…
On GPU, won't it be like BC3 compressed texture?
Alternate encodings like YCoCg tend to do better.
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#568Earlier quoted context omitted.
I still miss Battlefield 2. There is really nothing like it today, not even close. The dynamics with squads and a commander and A+ physics and overall game balance remain unmatched for all FPS games. Fortnite, PUBG, COD, all are disgraceful in comparison.
BF2 was great, BF3 was definitely better, not that there was anything at fault of BF2. I disagree with Fortnite and PUBG, whilst PUBG is a little clunky it did usher in a completely new game style AND importantly introduced much better situational audio which other games didn't have.
It might have popularized it, but PUBG was far from the first 'Battle Royale' game. Hell...I think it goes to those old Minecraft "Hunger Games' servers, but I'm sure it predates even that
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#569Earlier quoted context omitted.
That's because programmers in 2006 didn't understand programming. They didn't understand how to make their software better . Real programming means writing your own javascript glue, pulling in hundreds of supply-chain-compromised js libraries that you never inspect or profile, and running the whole thing in a browser engine, while making sure to store all state in the cloud. The modern breed of programmers who don't…
rust programs are a lot of times faster and orders of magnitude safer than C and C++ counterparts... where is your data to support your assertion that rust programs use more resources than C and C++ programs?
Re: Windows 11's built-in Weather app wastes more than 1 GB of RAM
#570Earlier quoted context omitted.
1MB is about the lowest memory usage you can get on Windows 7, because of reasonable tradeoffs made in the operating system to things like buffer and stack sizes. The OS creates a few threads for you, those threads have stacks and they didn't optimize the allocation size of those stacks - they used a currently reasonable default.
Depends on the app/framework but typically phantom threads don’t get started. Also, those stacks aren’t materialized until you write something - they’re all CoW’ed pages from a sentinel 0-filled page the kernel keeps around just for this purpose.