Windows 11's built-in Weather app wastes more than 1 GB of RAM

320 pointsposted 8 hours ago
by akyuu
(notebookcheck.net)

271 Comments

SBArbeit

5 hours ago

Easy workaround for this:

1. Install uBlock Origin in Edge.

2. Start Edge, browse to MSN Weather.

3. Click the "Add an Application" button in the address bar to get a Start Menu icon for the page.

4. Delete the in-box Weather app icon.

Now you get the same Weather app in about 130MB of RAM, with no ads. It's not as nice as a native app, of course, but it's 1000% better than the useless ads and MSN feed that you can't block from the built-in Weather icon.

(Also, go into Widget settings and turn off "Discover / Microsoft Start feed". Same crap, different surface. Get rid of it.)

aniceperson

5 hours ago

1. install ublock origin on Firefox.

not even being annoying, edge is removing manifest v2 very soon, breaking proper ad blocks just like chrome

rstat1

5 hours ago

I don't know if I'd say that's gonna break "proper ad blocks".

UBO Lite (the MV3 version of UBO) seems to work just fine in my experience, at the core function of being an ad blocker,

s3p

an hour ago

MV3 is severely limited in what it can do. One example that blew my mind is that chrome happily renders webpages immediately after application launch, while extensions are still loading.

Firefox, in contrast, doesn't let the network request fire off to the page until every extension is ready. So chrome is essentially screwing over the user, letting ads/ blocked content load, and intentionally degrading their experience, to make things appear slightly faster.

Catloafdev

4 hours ago

This is a narrative that MS, Google etc want you to believe. They gutted it for ads. That's what's happening. There are workarounds now, that's what the existing ad block options are. They are heavily kneecapped.

fakwandi_priv

4 hours ago

> According to Windows Latest, the high memory consumption is due to the fact that Weather is not a fully native Windows application. Instead, it is essentially an MSN Weather web app built on Microsoft's WebView2 framework.

I wonder how this approach is having such an high reduction in memory usage compared to what’s stated in the article. I would assume both use the exact same WebView here.

The only explanation here that I can think of would be that the “Add an application” starts it under an existing Edge process which shares it’s memory instead of completely isolated.

smileybarry

21 minutes ago

WebView2 has some memory optimizations across several WebView2 instances, so it should save memory once you have multiple WebView2 apps running.

Scharkenberg

2 hours ago

Yes, using an already-running Edge instance saves a bunch of memory. Also, this approach has the advantage of allowing all of your browser extensions to modify your Web-App experience. WebView2 doesn't relay Edge extensions.

dualvariable

an hour ago

The weather app isn't a native app either:

> According to Windows Latest, the high memory consumption is due to the fact that Weather is not a fully native Windows application. Instead, it is essentially an MSN Weather web app built on Microsoft's WebView2 framework. Task Manager shows multiple Chromium-based subprocesses running simultaneously, which contributes to the unusually high RAM usage.

If you have Edge or Chrome open (or anything else that similarly uses Chromium) then the incremental increase in RAM usage from the Weather app is likely much smaller than the headline 1GB.

ndriscoll

7 hours ago

My gaming PC that I built in January 2006 that IIRC I used to simultaneously run Battlefield 2, Trillian, Xfire, Thunderbird, and Winamp with a 1680x1050 monitor had 1 GB of total system RAM.

Melatonic

9 minutes ago

Think about all the performance you could have gained by instead running Trillian and Winamp on an old Thinkpad next to you with even less ram

dddw

25 minutes ago

Trillian, good old days. Still remember my icq number

GuB-42

3 hours ago

Putting aside the fact that it is horribly bloated. Accurately measuring RAM usage is tricky, there are several measurements, and no "right" one.

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.

The thing that the task manager doesn't tell you is whether or not these are shared components. It may be that the 662 MB used by the "Renderer" is shared between many Windows components, so killing that Weather app may not reclaim as much space as you may hope, instead, it would require killing every user of the component, some may be core system apps.

In addition to the distinction between private and shared memory, there is also the distinction between actual RAM usage and and virtual memory. It is possible for a process to memory map a 100 GB file. If you look at the address space, it will take 100 GB more of virtual memory, even though it may be actually zero physical RAM, but it is not always zero either, the parts of the file that are currently accessed take up some space, which may later be reclaimed by the OS by committing the page to disk.

Even the most obvious "I do a big malloc()" kind of memory use is not that obvious, the OS can overcommit, put stuff into swap, use memory compression, etc... And it can do that even if the system is not overloaded, as to make more space for the disk cache for instance.

So seeing "1 GB" in the task manager is just a vague hint of how it may affect performance. And not all "task manager" tools give the same value for the same program (so Windows vs Mac may be misleading). "Process Explorer", a more advanced version of the Windows task manager can give a lot more details, with different values of memory usage depending on what you are looking at.

ack_complete

3 hours ago

> The thing that the task manager doesn't tell you is whether or not these are shared components. It may be that the 662 MB used by the "Renderer" is shared between many Windows components, so killing that Weather app may not reclaim as much space as you may hope, instead, it would require killing every user of the component, some may be core system apps.

It is the other way around, shared memory causes Task Manager to _underestimate_ memory usage. Task Manager's default views report the process private working set, no shared memory included. This means that 662MB is the _minimum_ amount of memory commit that would be released by ending the process.

> the OS can overcommit

Windows does not allow overcommit by default. It may compress or optimize memory allocations to reduce the physical working set, but the kernel will start failing memory allocations once physical + swap is exhausted regardless.

calmingsolitude

3 hours ago

> It may be that the 662 MB used by the "Renderer" is shared between many Windows components

From the screenshot in the article, this is the memory usage of the Renderer process spawned by the Weather App. I find it very unlikely that some other app (say, the Copilot app) can then piggyback on Weather Renderer process. Do you have a source for this?

> killing that Weather app may not reclaim as much space

Closing the weather app on my PC does in fact kill all child processes and frees up around 1GB of committed RAM. Are you not seeing the same?

kasabali

an hour ago

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

waynesonfire

3 hours ago

> the 662 MB used by the "Renderer" is shared between many Windows components

Fine, shutdown the weather and stock ticker apps.

bullen

7 minutes ago

Why does Windows 10 use 10GB of RAM if you have a total of 32GB?

And how come you cannot pretend to only have 4GB to make it use less?

I don't care about how slow the OS becomes, I care about software not crashing.

Retr0id

a minute ago

Most of the RAM being "used" is available to be reallocated to something more important, should the need arise.

cogman10

5 hours ago

As time goes on, I become more and more convinced that OSes need some sort of OS level GC pool which all GCed languages play in rather than having the language runtime provide the GC.

A major part of why these sort of simple applications are taking gbs of memory is because the GC wants to simply grow as much as it can to avoid pauses/jank. There might be 10% of the memory which is actually live in that 1gb. But because it allocates fast enough, the extra headroom is needed.

Even if it isn't the case that the GC is universal, having a shared GC amongst runtimes would be a boon in general. If I have 3 JVMs running, I might give them all 1gb of memory even though really each of them only needs 200mb to get their job done. The extra headroom is for when a burst happens. If I could combine all 3 into 1, I could save a lot of allocation overhead and general memory.

This does sort of exist in java (war deployments), but there are limitations that make it unappealing. For example, each of the JVMs have to be the same version.

afdbcreid

2 hours ago

This is far from trivial. Consider the WasmGC proposal, which had a somewhat similar goal.

Then C# came and said "we can't use it, we have different needs". So did Go.

goalieca

3 hours ago

> A major part of why these sort of simple applications are taking gbs of memory is because the GC wants to simply grow as much as it can to avoid pauses/jank. There might be 10% of the memory which is actually live in that 1gb. But because it allocates fast enough, the extra headroom is needed.

There’s very minimal state for a weather app. You should be able to sweep the whole thing pretty fast. You could probably statically allocate most of that state.

Hackbraten

2 hours ago

> There’s very minimal state for a weather app.

Except when it uses some kind of browser engine to render its UI?

mwkaufma

5 hours ago

The ram usage in this case is an order of magnitude lower if you install ublock in edge, as other comments have noted. Why would a system level GC affect wasteful adtech?

Any marginal efficiency gains will be wiped out with more adslop. Nathan's law.

smileybarry

15 minutes ago

I don't want to "akshually" this, but on a stock[1] up-to-date Windows 11 x64 25H2 (aka: my desktop) Weather takes up around ~670MB of RAM at launch, not 1GB. While writing this comment it dropped to 450MB. All in all much lower than 1GB.

1: i.e.: not "debloated" or running a bunch of random customizer scripts.

gruturo

7 minutes ago

That doesn't take away at all from the complete absurdity of this level of bloat. How is it not 450kB? Fine, a few high res icons and multi language support, let's make it 4MB, because to do it in 1 would take skilled coders.

firefoxd

7 hours ago

This took me down a rabbit whole. Why can a simple single purpose app not be just a couple megabytes if not less? The popular options are electron 100MB+, or embedding python3 in your executable which is at least 40MB.

But if you build it natively, you should have all of Microsoft tools at your disposition, dlls and such. In theory, this should allow you to make a 1 mb app or less. But in practice, it's the worse option.

mort96

6 hours ago

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 means another 3840x2160x3x0.5 bytes for the pre rendered text.

3840x2160x3x3.5. That's 87MB, in pixel data only. And it's a very minimal example; for the parallax image, you're gonna want the image to be significantly taller than the window; you're gonna want a ton of smaller (tho still high DPI) images for icons; a few different font atlases for different font faces you've loaded at once; maybe pre rendered pixel buffers for all sorts of UI components; etc.

And lord help you if your designers want any part of this to be animated.

(I'm playing a bit fast and loose with what lives on the GPU and what lives on the CPU here. On many systems, they share a memory pool anyway. But on systems with discrete GPUs, most of this is gonna be video memory. Though applications may wanna store CPU-side copies as well for various reasons.)

201984

6 hours ago

>Your designers want

Sometimes, you need to tell the designers NO. Moving background images don't help people figure out what the weather is going to be.

therealdrag0

2 hours ago

Many people enjoy a tasteful weather app. Granted a “minimal” UX toggle would be easy to add to reduce memory for those who cared.

docjay

11 minutes ago

I think the issue is with the recent definition creep of “tasteful.” Seems you might have the same mindset if you consider “minimal” to be the other option.

LinXitoW

an hour ago

Sometimes, you have to realize Hacker News is full of nerds that care about stuff nobody else cares about. Looks are so fucking important for many normal people. There's people that decide for or against a phone simply because it comes in a fun color.

keicwifjwud

5 hours ago

And sometimes your engineers need to be a LOT less stingy. 1GB is clearly overkill for an app such as this, but ~300MB is perfectly acceptable if it works well, looks good and does what it should do.

There is such a thing as overdesign, but when you’re building a modern application, you must trust your designer’s sense of aesthetics and knowledge of UX patterns—two things engineers are often notoriously bad at.

gruturo

2 minutes ago

You're off by 2 orders of magnitude if you think that a not completely incompetently coded weather app genuinely needs that kind of resources - even allowing for aesthetic choices and modern UX patterns.

kasabali

an hour ago

> ~300MB is perfectly acceptable if it works well, looks good and does what it should do.

No it isn't. It isn't a word process for gods sake. It has one literally one job and 300 MB is like an order of magnitude off for that. This mentalty is the slippery slope that led us to the situation in the OP today.

christophilus

2 hours ago

Dunno. Many designers are pretty bad at UX. They’re OK at aesthetics, but that’s not the same thing.

mort96

6 hours ago

Honestly if the image is of the current weather it kinda does. I don't mind e.g Apple's weather app design at all

mrob

2 hours ago

You probably have a SVG renderer in memory already, and you already have a frame buffer and/or compositor buffer(s). Why should adding a graphical representation of the weather require more than a few KiB?

mort96

2 hours ago

Because a big picture looks pretty sometimes?

Not sure what you think "having an SVG renderer in memory" means exactly, typically the way an SVG renderer works is that you give it a huge chunk of memory and ask it to draw pixel data there from the SVG file. So even though the SVG is small on disk, rendering a 1000x1000 image from an SVG is gonna need a 1000x1000x3 byte pixel buffer (assuming no transparency or HDR shenanigans)

aucisson_masque

2 hours ago

> i'm playing a bit fast and loose with what lives on the GPU and what lives on the CPU here. On many systems, they share a memory pool anyway. But on systems with discrete GPUs, most of this is gonna be video memory

Yeah this is irrelevant here, windows doesn't share both in 99 of the case.

mort96

an hour ago

What do you mean by "windows doesn't share both"? Windows doesn't get a say, Intel iGPU systems literally don't have video memory

well_ackshually

2 hours ago

DWM quite literally does that all the time. For the general case it allocates GPU memory, but also swaps to system RAM or uses it as a synchronization mechanic when you have one screen on an igpu and the other on a dgpu.

firefoxd

5 hours ago

Good point. Though 4k image assets mean more that they look in 4k, not that their size is 4k. It might not be 87mb, but still way more than the couple mb I suggested.

well_ackshually

2 hours ago

??? Fast and loose is an understatement, at best it's a view from a rendering engineer that thinks all software acquires a DXGI swap chain and handles buffering itself, but it's flat out wrong and over two times too high at the very least.

* Not every app is full screen (especially not a weather widget.)

* Very few people actually have a 4K display. 1080p and 1440p cover over 75% of users already.

* You do not allocate a separate buffer for the main content and the parallax, applying a different transform does not need a dedicated buffer, just something the size of your asset. It can be a 640x480 upscaled asset for all you care.

* You also don't allocate a dedicated buffer for text rendering/hinting. Your text rendering engine keeps a texture atlas in a buffer which is eventually maaaaaybe reach a 4k texture if you display a TON of various glyphs, realistically they won't. DirectWrite will also share this atlas with other executables unless you explicitly ask for isolation.

* On windows, you write to DWM, which keeps a single buffet for all your windows. Every window does not pay that memory price. I'm pretty sure most compositors do something similar.

mort96

2 hours ago

* I never said all software handles the swapchain itself. The front and back buffers are obviously not usually allocated in user code. But they're allocated nonetheless and contributing to memory usage.

* Not every app is fullscreen, but I was using a maximized app as an example. If you make the window smaller then yeah obviously the numbers get smaller proportionally.

* A ton of people have 4k displays, it's difficult to find a moderately high end laptop without a 4k display these days. In any case, that was the hypothetical example I used.

* If you have a window that's roughly 4k resolution, and you want a background picture which fills the entire window, that's gonna be a roughly 4k resolution pixel buffer (unless you stretch a smaller image, but that looks ugly).

* Depends on the text renderer. I have mainly used pangocairo, which is based around CPU rendering text to a pixel buffer. I know that this is the typical recommendation for handling high quality rendering of longer pieces of text with Canvas on the web too. Maybe a typical win32 app actually does render each glyph fresh every frame from a font atlas, I'm not familiar with Windows APIs specifically. I apologise for the inaccuracy if that's the case.

* I'm pretty sure you're wrong here? If DWM has only one buffer which all windows share, how does it handle the case where a partially obscured window goes unresponsive for a bit as the user removes what obscures it? In old school non-composited X11, the answer is that the X server paints in the newly revealed area with grey pixels and asks the window's process to re-render that region, causing a lingering grey region if the app is frozen. Preeeetty sure that Windows 11 doesn't do that. But do you have documentation on this?

ashleyn

5 hours ago

A lot of these applications run in Electron or similar libraries where a whole new browser instance, with all its overhead, is stood up for each application. The simplest answer is we need to stop trying to use web technologies as a one-size-fits-all GUI toolkit.

lelanthran

4 hours ago

> This took me down a rabbit whole.

The rabbit was too hungry to even stop to chew you?

firefoxd

2 hours ago

Haha, and it's far too late to edit!

fuzzfactor

2 hours ago

Beware the rabid rabbit and don't let your whole near his hole . . .

trzy

6 hours ago

The visual assets alone will be tens of megabytes.

anonymars

6 hours ago

Why, though? You need some icons and some map imagery, not 4K texture maps

chneu

6 hours ago

Its 2026. You need 4k assets for job security.

Micrococonut

6 hours ago

Should be able to get by with using system graphics

SV_BubbleTime

6 hours ago

Do all visual aspects of a weather app need to be loaded at once? Is the cost penalty loading a hundred kilobytes per image from disk really unacceptable?

doikor

6 hours ago

Even if the app is no longer using that memory it is not released until Windows thinks another app needs it.

vel0city

6 hours ago

And then people complain about how unresponsive applications are, all these little stutters as things pop in.

iAMkenough

6 hours ago

For a weather app, you should be able to get by with a couple base vectors you modify based on conditions.

mort96

6 hours ago

On disk yeah, sure. But you're gonna render them into a pixel buffer which lives in memory.

samrus

6 hours ago

How did applications do it before? Like in the 90s or 00s

mort96

6 hours ago

WAY lower resolution screens so pixel and frame buffers were a tiny fraction of the size, non-composited graphical environments which meant there was one fewer frame buffer per window, and a visual style which typically emphasized large pictures/animations less.

nicoburns

6 hours ago

They had fewer graphics, and much lower resolution screens.

Dylan16807

6 hours ago

Windows 98 SE kind of went overboard with the graphics (remember Active Desktop?), and a common screen size at the time was 1280x1024. But if you run modern stuff at 1080p (60% more pixels) or 720p (fewer pixels), you're not going to see comparable memory use.

mort96

6 hours ago

Windows 98 wasn't composited, which makes a huge difference.

And to be clear, there's a ton of unnecessary bloat today as well. It's just that even a lean and mean highly hand optimized native app is gonna be way bigger today than it was then, due to compositing, higher resolution assets, higher resolution screens and different design sensibilities. But most apps aren't lean and mean highly hand optimized native apps so.

Dylan16807

5 hours ago

Compositing means you can excuse an extra dozen megabytes per megapixel of window size. The window in the article is less than a megapixel. That factors in the relevant part of screen resolution too. High resolution assets should scale alongside window size too, adding a fraction of the above dozen megabytes.

And I'm saying 98SE already had image-heavy design sensibilities all over.

You don't have to highly hand optimize to run a weather UI in a lean way.

vel0city

6 hours ago

> and a common screen size at the time was 1280x1024

Maybe if you were really rich and only used high end desktops. A lot of the computers I used back then were still 800x600, fancier ones were 1024x768. If you happened to also have a 2D accelerator card you'd potentially have 1280x1024. And lots of apps purposefully ran at a much lower color depth, it was common for games to run at 8 or 16 bit color mode.

koyote

an hour ago

Early 90s maybe. By the end of the 90s and definitely early 2000s CRT screens were 1024×768 for the cheap crap and 1600×1200 for the high-end (with 1280×1024 as a mid-range).

kasabali

an hour ago

Cheapest local brand 15" CRTs could do 1280x1024 in early 2000s. because you weren't limited by the panel unlike LCDs.

You'd need better than perfect vision to be able to make use of it, though.

Dylan16807

5 hours ago

I saw a lot of computers set to 800x600 but I don't recall any that couldn't be switched to at least 1024x768. Which is still quite close to 720p for making this comparison.

And yeah lots of fullscreen-ish things ran in lower color, but this is about desktop mode and I never saw a desktop mode that struggled based on color depth.

znpy

6 hours ago

It can, but you have to know what you’re doing and you have to know it very well.

Looking at the opposite extreme, the guy that originally wrote the windows task manager (the thing that popped put when you pressed ctrl+alt+canc) posted a video about cloning the windows basic text editor in a 3kb binary: https://youtu.be/OG91c7xsNMc

Needless to say, the guy knows what he’s doing.

itopaloglu83

7 hours ago

And it also ads on it.

Really Microsoft? Do you really need all the ads revenue from the weather app?

What’s next? Ads on the start menu?

mort96

7 hours ago

Microsoft absolutely doesn't need it, but I'm guessing the weather app team (or the core filler apps team or whatever team is responsible for it) needs it to juice a metric to make some middle manager happy.

And it makes the middle manager happy because it lets that middle manager report better numbers to their superiors again.

Etc.

It's why all large dysfunctional organisations do self destructive stuff like this.

SlightlyLeftPad

7 hours ago

“What value are you bringing to the company?” translates to “if you’re not printing money, you lose your job.”

dasyud

6 hours ago

I once worked on a project where the goal was to improve the reliability of MS Teams. The skip level manager was not happy when we said we cannot estimate what the revenue gain would be because it can't be measured.

mpyne

4 hours ago

This risks getting into the Fisherian/Bayesian stats wars again, but it would be possible to project a revenue gain, even in advance of making the change. You'd do this in terms of improved customer retention, lower cost of future customer acquisition, increased price a Teams license could sustain based on a rep for higher reliability, etc.

Obviously it's not a change that you'd be able to pin a specific human decision-maker (who was marginal on Teams) down as to this change being the difference between a sale or not, but nor is the change in revenue going to be a random number uniformly distributed in (-∞,∞).

If the change was revenue-neutral, the skip level would probably have been justified in seeing if the teams working that project could have found something to do customers actually care about instead.

mapontosevenths

6 hours ago

Any manager who doesn't push back when given a perverse incentive should be fired. They are not leaders, they are followers... And not even very good followers.

mort96

6 hours ago

Yet they're the ones who get promoted because their KPIs are the best.

bossyTeacher

6 hours ago

They do. Never forget, Microsoft's goal is to squeeze as much money from you as possible.

dabinat

6 hours ago

That’s the goal of every publicly-traded corporation in a mature market. Wall Street demands ever-increasing returns and they can’t grow their customer base much so cost-cutting and fleecing existing customers are the only levers to pull.

hadrien01

an hour ago

What's worse is that the previous version of the same Weather app was fully native on Windows 10. Why would you take a perfectly working app and downgrade it like this?

tonypapousek

an hour ago

Well, this is Microsoft and Windows; it would be weird if it got better.

eviks

7 hours ago

> By comparison, Apple's native Weather app on macOS reportedly uses less than 250 MB of RAM

That's also bloated, couldn't they find a better comparison to illustrate the egregious waste?

jlg23

18 minutes ago

Thank you. And it is a shame I had to scroll down this far in the comments for someone to point out the obvious. Even a weather app that uses "only" 250MB of RAM should never have been delivered by a semi professional software shop - 250MB is enough to store whatever they can display in full screen on a 5k display as a bitmap - 5 times.

nashashmi

7 hours ago

It’s an equivalent app to make a comparison with, one from an OS company.

But yeah, I still remember when a weather app would take 10 MB and I was complaining (1999)

lambdaone

3 hours ago

250 MB is exactly the sort of bloat you'd expect from this sort of daft web-browser-wrapper application, and Apple get it there. 1.2 GB, on the other hand, is 5x as much, and completely insane even when you start off with daft as your starting point.

danpalmer

2 hours ago

Apple weather is fully native from what I understand. I suspect the 250MB comes from the video backgrounds they play. Arguably that would be a reasonable thing to sacrifice on low memory systems, you'd barely notice.

odo1242

an hour ago

I was able to do some tests with AI agent help and got:

- ~45 MB on buffers for animated backgrounds

- ~10 MB used for the Swift language runtime (runtime type information)

- ~44 MB used for system libraries: libSwiftCore, CoreFoundation, libobjc, Metal, VFX

- ~21 MB used on GPU buffers (GPU memory is also part of used system memory because of unified memory)

- ~6.3 MB for the weatherd daemon that actually collects the weather info and makes it available to the weather app and to widgets

- ~6.2 MB used for the display color pipeline (to handle color gamuts proprtly)

- ~7 MB runtime caches (shader compiler cache, libobjc cache, etc.)

- ~1-2 MB used for particle effects

- ~34-40 MB of memory as general heap memory that was otherwise unaccounted for (this seems to mostly be stack memory and threading-related stuff, and the actual application logic)

Overall the app is relatively optimized

derac

4 hours ago

I prompted my own windows taskbar weather app in rust with radar and forecasts and it's 233 kB.

https://github.com/derac/WeatherTray

I use Linux now, so you're on your own if there are issues. It might require some windows library to be installed but I don't recall. I ran it for a long while on win11.

fuzzfactor

3 hours ago

That's embarrassing.

Not your app, it rocks.

Microsoft. It's like some decision-maker thinks it's OK to waste memory as long as it's someone (everyone) elses' memory, but it really adds up if you know anything about scale.

But what they're also doing is a non-businesslike under-utilization of their own resources.

Which is disgraceful in itself on top of that.

They're supposed to have much better AI than average and nobody even bothered to ask ChatGPT why in the world weather should take more than kilobytes?

And if their AI can't do it autonomously in under a megabyte it should be able to give a plausible explanation why not by now, and at least it would be orders of magnitude better than a gigabyte.

I assume yours went smoothly as prompted and it surely is an excellent example :)

sssilver

2 hours ago

> It's like some decision-maker thinks it's OK to waste memory as long as it's someone (everyone) elses' memory

My friend, you're giving them way too much credit.

Nobody, especially no decision-maker involved with this, has ever spent a single thought anywhere near any concept related to memory.

It just literally never crossed anyone's mind.

userbinator

2 hours ago

They're supposed to have much better AI than average

I suspect there will be a bit of revelation once people realise how much better AI can make software if prompted correctly. Of course a lot of slop will always exist, but things like https://news.ycombinator.com/item?id=49226923 show that it can be a powerful force multiplier if used right.

glimshe

5 hours ago

10MB to tell me the weather from a remote server...

Let's remember that the sprawling world of Legend of Zelda SNES (a Link to the Past), including all graphics, music, code and dialogue was 1MB.

inigyou

an hour ago

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.

vlovich123

an hour ago

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.

dwattttt

37 minutes ago

It's been a while, but I believe Windows initialises an internal thread pool & parallelises (some parts of) process start / module loading

vlovich123

7 minutes ago

You’re right. I hadn’t realized that Windows creates a hidden thread pool under the hood for parallelized DLL loading.

beloch

3 hours ago

What else might that weather app be doing to justify the memory footprint? MS might suck at memory efficiency, but you can't claim they'd ever miss an opportunity to monetize their users. How can a weather app make MS money? MS has asked themselves this, so maybe we should too.

usea

3 hours ago

You're right that it's a matter of incentives, but it's because of cost not revenue.

It's bloated not because of a sneaky plan to include revenue generation. It's cheaper to make it bloated because quality is costly. They can externalize costs to users and nobody cares.

TitaRusell

2 hours ago

I play videogames. As soon as it became technically feasible to patch games we began to see videogames come out with first day patches.

When you take away the constraints the slop emerges. You could not make mistakes in software when it was all printed on CDROMs and DVDs.

smelendez

an hour ago

I remember playing The Elder Scrolls: Daggerfall in the 1990s. It came on CD and was very buggy, and I would periodically call Bethesda and they would send me the newest patches on a floppy disk.

blackhaz

6 hours ago

10 MB is ridiculously overbloated. 1 MB or something in that vicinity should be more like it.

magackame

5 hours ago

I think you guys on HN can be a bit out of touch maybe? On my linux machine (measured with tux-manager):

  nautilus                            177 MB
  kitty                               150 MB
  alacritty                           107 MB
  mpv --idle --force-window           160 MB
  winit empty window + OpenGL context 100 MB
  tux-manager                         69  MB
  hexchat                             55  MB
  gnome-terminal                      47  MB
  st                                  12  MB
  xterm                               12  MB
All these apps are what you would consider native, good apps. Written with Qt, GTK, some in low level langs like C\C++, Rust as well. There is of course different ways to measure the usage and maybe some more testing needs to be done, but stuff like 1-10 MB seems completely unrealistic. I think any empty Qt/GTK app eats 40 MB at least. Only thing that even gets close is st at 12 MB. And mind you it's a terminal (which is 1000x simpler than any modern GUI app, doesn't load any assets etc) and it doesn't even use any GPU accel (which itself seem to add a lot of baseline cost).

Honestly I was a bit surprised myself. I have a Rust winit + ash vulkan hardcoded triangle demo app and it eats 86 MB (the binary itself is 5.5 MB). I would love to know, if anyone could explain why GPU accel seems to eat up so much RAM. Like yeah, there are a bunch of images that live on swapchain, but they should all be in VRAM. Outside of that I don't see what would require MBs worth of overhead.

preg_match

4 hours ago

Yes these are all very, very complex applications though.

But I agree: using more memory is good, actually, because it means more stuff is being cached. Nautilus is probably pre-indexing directory structure so it doesn't have to read disk every single time you open your home folder. That's good. Oh, and thumbnails. Thumbnails are incredibly expensive memory wise, but very useful!

Also modern apps have A LOT built-in. Tons of font management stuff, accessibility, they work on many different environments. I mean, look at everything that goes into a modern terminal emulator.

But... a weather app is much simpler, IMO, than Nautilus or Kitty.

torginus

4 hours ago

Counterpoint: Nautilus is both slower and less stable than Windows Explorer on large folders, even though the Linux filesystem is much faster. These super-indexed desktop linux search functions are also dog slow, while `grep` and `find` in the terminal are much faster (for searching inside files), and those certainly don't cache anything.

preg_match

41 minutes ago

Windows Explorer crashes for me about ~3 times a day at work, and takes down the taskbar with it, so not sure about more stable. I don't use Nautilus though because it's pretty bare bones compared to Dolphin. Also:

> These super-indexed desktop linux search functions are also dog slow

Baloo-indexed KRunner on Plasma is instant. I index my entire home folder, including hidden files, and I can substring search with imperceptible latency. I can't speak to other search implementations, but yes KRunner + Baloo is much faster than grep.

okasaki

44 minutes ago

Thunar is very fast compared to Nautilus.

kasabali

2 hours ago

> Nautilus is probably pre-indexing directory structure so it doesn't have to read disk every single time you open your home folder. That's good

No it isn't good, and no it probably doesn't because it is kernel's job. I'd rather they don't do double caching, and it's actually worse if they do.

preg_match

40 minutes ago

Syscalls are expensive. It's not double caching, it's layers of caching. The kernel caches inside kernel memory space, sure, but you still need a syscall to reach that. Every application has layers of caching, it's very normal. This isn't even the top layer of cache, because of course the CPU itself has multiple caches.

But, for example, in a web application you will commonly cache requests. But then the database also has a cache. And then the filesystem the database is on also has a cache.

kvemkon

3 hours ago

> I think any empty Qt/GTK app eats 40 MB at least.

Classic GTK is (much) better (RSS on Linux):

  GTK2 14 MB
  GTK3 24 MB
Once it was decided that a desktop application must have fancy animation effects (like on smartphones) and be rendered completely on GPU things got very different:

  GTK4 98 MB

goalieca

3 hours ago

GTK used to be considered the bloated option along with QT. My first Linux box had 128MB of ram and it was screaming fast.

Joeri

2 hours ago

At one point I ran graphical linux on a 20 mb ram laptop although admittedly that was very tight.

I also remember running nt4 with photoshop, word, and my IDE (borland delphi) all at the same time and comfortably in 128 mb of ram.

inigyou

an hour ago

What was the lean option?

kasabali

2 hours ago

> mpv --idle --force-window 160 MB

That's still a HUGE amount when you remember mplayer (which mpv was based on) ran on PCs that has had less RAM than that.

torginus

4 hours ago

These apps have codebases going back to the 2000s when having 256MB ram total was a big deal, yet these apps could contend with that (while offering pretty much identical functionality). I remember one of the big arguments for GTK against Qt was that C++ relied heavily on templates, thus every C++ app would have their own copies of the same functions in RAM, while GTK was C, and a lot of those library pages could be shared. Qt even did some nonstandard tricks to cut down on this duplication, which was unpopular with the C++ people.

danudey

an hour ago

My Windows 98 install got ten times faster when I went from 32 MB of RAM to 48 MB of RAM.

A fresh boot of my Windows 98 install at the time, once everything was loaded and settled, used up 27 MB of RAM, meaning that after 5 MB of allocations someone was getting paged out somewhere. That extra 16 MB made a world of difference.

Do bear in mind, though, that we're dealing with a lot more than we were back then. Our hardware is more complex, with more and more complex drivers needed to manage more things. Accessibility is different, screens are larger (my monitor now has 27 times the pixels as my monitor then) meaning more memory required for larger textures which are now composited in hardware rather than re-rendered every frame.

I agree with others that things are ridiculous these days, but it's also easy to see that our expectations also need to adjust somewhat. Still, using a webview for displaying the weather... I get why they do it, but it's a scourge. It's emblematic of their care for the customer, which is nonexistent.

inigyou

an hour ago

Casey Muratori has complained about the hardware driver overhead, because it is possible for hardware to have standard interfaces without needing a device-specific software translation layer, especially for more basic modes (like framebuffer).

ahartmetz

3 hours ago

AFAIK, Qt's C++ extensions (moc, meta-object compiler) have nothing to do with how it reduces template bloat from containers, which is by moving some type-independent implementation parts to shared methods.

inigyou

an hour ago

Yeah, most of modern Linux wastes memory too. 100MB for a blank OpenGL context? Ridiculous.

Const-me

6 hours ago

10 MB is not too bad for a GUI app. If the app is full screen, display is FullHD and has 8 bit depth, that's almost 8 MB memory for the back buffer alone. Enable HDR and pixels become 8 bytes RGBA16_Float instead of 4 bytes BGRA8_Unorm, twice as much memory.

anabab

5 hours ago

2 bit 160x144px ought to be enough for anything

khazhoux

4 hours ago

Look at Richie Rich over here with his 2 bits!

perching_aix

5 hours ago

This is only relevant if we assume CPU rendering. The article described system RAM use, not video RAM use. Task Manager doesn't combine the two.

They clearly spent it on maintaining their independent Chromium instance instead.

torginus

4 hours ago

One thing shared between old software rendered desktops and modern videogames is that they shunned these intermediate 'composited' screens. On the desktop, there used to be the screen, and basically windows used to draw on top of each other, there was no intermediate buffer for the whole window to draw itself to, which would then be smushed together with all others.

Video games are the same (mostly) - everything is rendered in screen space for performance reasons, it's very, very rare, that you would render something into a temporary buffer then composite it on top of the rest of the scene - you would need exceptional reasons for that.

Maybe it's time to get back to the olden days of display servers - where applications would push a list of render commands to the 'display server', which would consist of rendering primitives, which would then take these commands and construct the whole UI on the screen, without the intermediate steps of each app drawing into its own little buffer.

You could always fall back to drawing your own applciations, then asking the display server to composite that, but that would pretty much be the exception, not the norm.

goalieca

3 hours ago

This would really help responsiveness. Keypress to pixel is a huge issue in these bloated frameworks which are running on top of bloated OS

Const-me

4 hours ago

True, but many modern computers are using unified memory. On such systems all memory is almost equal, despite often reported differently.

For example, on my 5 years old laptop with integrated AMD GPU, windows 10 calculator in default state uses 33 MB system RAM, 9.6 MB dedicated VRAM. Maximized to FullHD screen, same app uses 36 MB system RAM, 13 MB dedicated VRAM. Maybe the OS counts VRAM as active private working set, maybe the app uses more than 1 buffer.

Regardless of the reason, it’s IMO unrealistic to expect a modern GUI app to consume less memory than required for the frame buffer for its window.

david-gpu

6 hours ago

How much money are these companies going to make by reducing their weather app to 1MB, or 10MB? How much is it going to cost them to get there?

The world doesn't run on personal aesthetics, when nobody is willing to pay for them.

LinXitoW

an hour ago

Hey, just a few more years of rising memory prices and it'll actually be a marketing term how much RAM something uses.

nashashmi

6 hours ago

These days we have an AI system to do exactly this kind of optimization, too expensive for humans, and too cheap compared to consuming expensive modern hardware

fragmede

6 hours ago

The MacBook Neo has only 8GiB of RAM. This is widely decried as not enough. The RAMpocalypse means that 8 GiB is going to have to be enough or else it'll eat into Apple's margins. The Neos are wildly popular though because people have used it and 8 GiB is fine. So while the singular weather app being smaller itself isn't material, in aggregate, macOS being more efficient is something that lets Apple sell a lower spec product while still justifying a higher price and thus better margins for Apple.

binaryturtle

4 hours ago

`ansiweather` needs like ~6.28 MiB (measured with `/usr/bin/time -l` on OS X), but it's a bash script that invokes cURL, so there's certainly various overheads there too.

One probably could get this down way below ~1 MiB with a properly tuned straight executable written in C (best not to use any of the "modern" stuff like Rust and Go, their default binary sizes for outputting "Hello, world!\n" are already extreme :-) )

By default anything needs at least 532480 bytes RSS on OSX (I tested it with the most minimal C hello world), so that's a threshold one probably can't beat on OS X at least. We probably could kill that value on Amiga OS with the exact same functionality. :-)

user

3 hours ago

[deleted]

cdud3

6 hours ago

The KDE Plasma weather app takes in maximum 1MB.

lynguist

6 hours ago

I'm not sure if you're reply hunting or we talk about different apps but how would you fit the Qt runtime, Javascript runtime, font cache, graphics, networking libraries, etc in this limit? This can't physically be under 70 MB, and more like 100-200+ MB.

Telaneo

5 hours ago

Many of those things are already in memory just from running an empty desktop.

rpdillon

5 hours ago

Sibling comment called it: these are dynamic libs used by the desktop, so the incremental RAM usage is low. That's a good approach! Makes me wonder what the heck MS is doing to get their app to add an incremental gig to memory usage.

khazhoux

4 hours ago

Even 1MB is too much. I expect a modern weather app to be <20K.

cogman10

6 hours ago

My entire kde "plasmashell" which includes my wallpaper and the various widgets installed (including a weather widget) uses 560MB for a screen with 5120x1440 pixels.

monster_truck

6 hours ago

That's still 26x more than the size of the display buffer, I would never settle for such bloat /s

loehnsberg

6 hours ago

I built a weather app for myself fetching ECMWF ensemble forecasts for my home location. Running the service is 60mb plus data 39mb and another 2mb for the spaghetti charts showing temperature, clouds, precip, wind over 10 days. What do I need to do to fill the other 900mb?

zapkyeskrill

6 hours ago

Run those things as an electron app? Add on analytics, location tracking and data exfil and you'll be fairly close

userbinator

4 hours ago

The article now says for me "By comparison, Apple's native Weather app on macOS uses roughly five times less memory under similar conditions."... which is not exactly the same wording.

Edit: I see the "250MB" line later in the article. This article is itself bloated for repeating nearly the same thing again.

thrance

4 hours ago

The most lightweight solution I can think of is:

   curl wttr.in

3eb7988a1663

an hour ago

That's basically my weather app. Though, I made it fancy at 7 lines of bash which takes location arguments and pipes into jq for display.

gruturo

10 minutes ago

In the era of coding with frontier LLMs, it should take Microsoft 20 junior engineers, a couple seniors, a token budget and a month or two to fix most of this shit by building lean, native apps. Given that they can obviously spare this kind of resourcing, I truly wonder why they won't. Not that I give a crap - removed the last windows machine from my home ages ago at this point.

userbinator

4 hours ago

After seeing https://news.ycombinator.com/item?id=49226923 show up here, I'm now hoping someone will vibe-code a nearly identical-looking native app that takes a few orders of magnitude less RAM.

Personally I just use my government's website when I need to check the forecast.

Hackbraten

2 hours ago

I’ve used Wego [0] for roughly a decade. It’s been good enough for me.

Six years in, I had to edit the configuration file once (to switch weather backends because the default backend shut down). In January, it’ll be 10 years.

[0]: https://github.com/schachmat/wego

eisbaw

2 hours ago

Why does everything turn into a browser

oblio

2 hours ago

Because Jamie Zawinski was right and also wrong. Everything evolves into a browser, which, yes, can also read email.

hyperhello

7 hours ago

I would like to be assured that the author knows the difference between actual memory and setting aside paging space.

tredre3

5 hours ago

The author doesn't need to know the difference because the task manager is accurate by default. I can still offer you some reassurance:

- The Windows task manager's memory column is the private working set which is the actual memory used by the application minus shared memory (but only shared memory that is currently shared with other processes, not merely marked shared. I.E. it's similar to RES - SHR on Linux but it's more accurate)

- Windows doesn't overcommit memory. Memory that is reserved but unused (not touching all pages) by the app is truly wasted. I mention this because in your other comment you make it clear that you think this is happening. But Windows isn't Linux.

benj111

7 hours ago

That still isn't a good look.

hyperhello

6 hours ago

I’m not sure if you mean a good look for the process or for the author but paging space is just saying “gimme a gigabyte” like saying “gimme a plate” is at a barbecue. The resources themselves aren’t being used at that point.

debazel

4 hours ago

On Windows over allocating virtual memory (commit charge) is still bad. Unlike on Linux, once the total commit charge hits your physical RAM limit + SWAP limit, Windows will start crashing your applications and refuse to allocate more virtual memory, even if that memory has not been touched yet.

This is also why it is very important to have plenty of SWAP space on Windows, even if you have 64 GiB+ of memory. Because applications love to over allocate commit charge.

benj111

an hour ago

As in it's sloppy.

If you're at a BBQ would you take 5 plates just because?

w4yai

7 hours ago

Please, Microsoft, PLEASE ! You can do BETTER ! Stop acting like an internship for every single feature you add ! Where's the money going ?

BuyMyBitcoins

2 hours ago

They can, but they won’t. Microsoft is run by the most cutthroat sycophants you could possibly imagine. That money you mentioned is going to those aforementioned sycophants and shareholders.

fsflover

4 hours ago

But will the earn more money by offering a better weather app?

iamcoder18

7 hours ago

This article seems to be underestimating how much RAM a weather app should take. A well thought-out, native Weather app wouldn't take more than 100 mb of RAM.

karmakurtisaani

7 hours ago

This has strong "How much could a banana cost? 10 dollars?" vibes.

Back in my day 100MB was all you had for all your compute, and somehow programs still ran.

whynotmaybe

7 hours ago

Back in my days, I had to remove the mouse driver from autoexec so that microprose grand pirx had 600kb of ram to start

SV_BubbleTime

6 hours ago

Had to get a ride to drive floppies with corrected config.sys and autoexec.bat files around to friends.

Things weren’t actually worse.

iinnPP

4 hours ago

Personally, I have reverted back to sneakernet in a lot of what I do.

kevin_thibedeau

7 hours ago

When RAM was $100 per MB that would be $10,000. You can do a weather app in much less provided you use native code.

big85

7 hours ago

LumiWeather for AmigaOS runs on 2 MB RAM.

drdaeman

7 hours ago

ESP32 in my OpenSprinkler pulls the weather (among a few more things it does) just fine and it has 520 kilobytes or RAM total.

2Gkashmiri

7 hours ago

Windows really I'd shitty for "assuming" unlimited ram, storage, processing, internet budget for them to get away with it.

They "could" make it easy but why bother? I assume next update will make calculator 1 gb download, 2gb ram resident and ADS

keicwifjwud

5 hours ago

> Back in my day

Back in my day systems used to be a lot simpler too. These “back in my mind” comparisons show a clear lack of understanding of the subject matter. 1996 apps are not the same as 2026 apps. Expectations are different. Design languages are different. Even the UX is entirely different.

1GB is clearly overkill, no question. But ~100MB to ~300MB is perfectly reasonable and you know it.

karmakurtisaani

2 hours ago

Yeah I wrote it a bit tongue in cheek, but even then I can't help but wondering where is all that memory needed.

My best guess is the GUI is somehow really heavy, wouldn't expect a simple console program that connects to some weather API to require that much RAM. But I never worked on apps like this, so no clear idea.

vinyl7

4 hours ago

99% of apps have the same or less functionality today as they did in 2001, but are significantly slower and worse.

chrisandchris

4 hours ago

Functionality isn't everything. A human teller has the (more or less) same functionality as online banking, but I do love me some online banking.

I also like the weather icons being 4K and having some smooth anmiations.

Not to say that it's gone worse (it has IMHO) but comparing 25 years ago to know doesn't help much. Times were different back then. That's like comparing 1900 travel to today.

e2le

7 hours ago

What is the weather app doing that it requires 100MB? For such a simple application, that seems excessive.

kevincox

7 hours ago

Mostly rendering. A bunch of images, text, UI elements. On a modern high resolution display it adds up quite quickly. You can surely cut it down a bit, but 100MB isn't absurd.

charleslmunger

7 hours ago

A weather widget using 8 bit color plus alpha on a 4k display show three full size images in 100mb. But I suspect that's not the ux we're talking about here, and a widget style system has no excuse.

galad87

7 hours ago

Apple's Weather app has an animated background, glassy views, and nice animations like water droplets on the glassy views when it's raining. So rendering all that on a 4k or more display at 10bit depth is going to consume a bit of RAM. However I guess it can surely be improved to make it consume less RAM.

anthk

6 hours ago

Vector icons. It can be fit under 50MBs.

pixelesque

5 hours ago

Those still have to be rasterised to a pixel-based frame buffer at render/compositing time.

useasvg

7 hours ago

Use an svg.

Or render everything using css, 100mb is someone not trying. 1gb is absurd abuse that only domestic violence victims put up with.

preg_match

4 hours ago

SVG is an on-disk format. It has to be rasterized, otherwise how do you have pixels? Each pixel takes up memory.

qlm

7 hours ago

Quite a tasteless metaphor, no?

Dylan16807

7 hours ago

If I full-screen it in high enough resolution it can be excused for using 100MB temporarily.

The window in the article wasn't very big. At most it would have about 10MB of framebuffer, and the images on display would fit into 1MB uncompressed.

We can't excuse typical program waste with screen sizes. Especially when you can switch to 1080p or 720p and watch them still use massive amounts of memory.

cyberrock

6 hours ago

I think this depends on your location, because in some places you really want to view a radar map. "Rain in $CITY" is practically useless for me. Still, the (static?) map in the depicted app shouldn't take 1GB.

lousken

7 hours ago

I am pretty sure xfce4 weather plugin takes a lot less.

Throwthrowbob

6 hours ago

Looks like about 30 MiB with a quick test.

satvikpendem

7 hours ago

You don't need anything more than https://wttr.in/ even with all the fancy terminal graphics.

blooalien

2 hours ago

They also have a nice API where you can pull the raw weather data and fancy it up any way you like graphically. Great for building your own entirely custom weather widget for your desktop, webpage, app, or whatever. :)

cissikatt

4 hours ago

Why would I like to know the weather in some other city?

satvikpendem

4 hours ago

What do you mean? It gets the weather for your city via your IP address, maybe you're on a VPN.

Narishma

2 hours ago

Your IP address doesn't automatically correspond to your city, even without a VPN.

satvikpendem

2 hours ago

Then add your city as an argument to the curl. It works well enough regardless and doesn't use hundreds of megabytes of RAM which is what the initial complaint was.

benj111

7 hours ago

Well it's comparing it to apple's weather app, which is a fair comparison I suppose. 100mb still sounds like at least an order of magnitude too high to me though.

feverzsj

7 hours ago

It's just msn weather page. Can't they use one single browser for all their apps instead of one per app?

whynotmaybe

7 hours ago

No, because you have to manage communication between different teams on "how" and "what" about the single browser, much easier to let every team do their "best" without any external interference

CrimsonCape

6 hours ago

Yesterday I was running : NixOS, mango window manager, 5 instances of ghostty, 2 of those running fresh terminal editor, firefox with 5 tabs and I was at 2.37gb of RAM.

matteoraso

2 hours ago

RAM consumption has gotten crazy over the past couple of years. Consumers need to start calling software devs out for this, especially when there's such a severe shortage of RAM.

mickelsen

an hour ago

They could ask AI to refactor and debloat, since they can't be bothered with it because the incentives don't seem to align.

Last decade has been the worst, not even worth it for the eye candy like before.

kmfrk

5 hours ago

Shame, because it's genuinely a great map - ahem, optimizations aside.

I remember giving the app a second chance - after assuming it to be bloatware next to all the other default apps that came with Windows - but after seeing it redeem itself in benchmarks[1], I gave it a shot and quite like it. The iOS app was too rubbish to bother with, though.

I'm curious what could options there are for decent predictions. Especially with Dark Sky never having been much of an option for Europe. I see some of the people behind it have a new subscription-based iOS app to try, though: https://acmeweather.com/app.

Do people have any desktop weather apps that strike a nice balance between decent code and actually useful predictions? Future weather's likely to be anything but boring, unfortunately.

[1]: https://forecastwatch.com/awards/2026/

SSLy

5 hours ago

My country's agency for weather and water mgmt has consistently the best 48h forecast. Try looking for an equivalent in yours.

alkonaut

5 hours ago

I wonder if this is a fair calculation including the fact that multiple WebView apps should be sharing the same libraries in memory.

If you pay 0.5-1GB to load the edge/chromium libraries but that memory is amortized over N different apps the user is likely to run, then the ”1GB for the weather app” is an unlikely worst case.

Dwedit

4 hours ago

This is what happens when you start a separate instance of Chromium everywhere.

hokkos

7 hours ago

Apple Weather app can jump to 1GB on a mac if you click around a little with the wind gust direction particle effect in the map

Zopieux

30 minutes ago

What's the status on automatic debloating (non interactive) scripts for Windows these days? With vibe coding I'd expect hundreds of those to exist by now. Something everyone would run after a clean install, to revert, disable or uninstall all the stupid defaults and enshitifications Microsoft added in the past decades.

Anyone can recommend one of those?

polyterative

an hour ago

I am using AI to rewrite every proprietary driver/companion soft I had still running on my Mac system.I am using 5/10% of the original application's RAM.I am getting more features.My background RAM usage halved after converting many of them to my own versions.

cherryteastain

an hour ago

For comparison, the GNOME Weather app takes 80MB.

cromka

5 hours ago

I seriously wonder if the recent migrations between languages mande by major projects leveraging SOTA LLMs have started a new trend of a) making native apps more common, as opposed to Electron and stuff b) will help to optimize existing apps and remove the bloat.

The alternative is, of course, that most apps will end up being bloated even more specifically because of how we'll slowly transition into developing using LLMs only.

TacticalCoder

6 hours ago

All the comments excusing the RAM usage "because high-resolution screens require pixels" are missing the fact that there's this thing called GPU memory. Which is where pixels data should be. There's no way you need to store fullscreen 4K images for a weather app on anything else than the GPU: use scalable icons, render them on the GPU. No need to use actual RAM: the GPUs have had their own RAM since times immemorial and GPU rendering is a thing too.

drtournier

7 hours ago

PC games were the last reason why I still used windows. Now that Proton works wonders in Linux, I hope I don’t need to ever come back again. Great times with 98, xp and win7 that were snappy, easy to install and with no slop

strong-self

5 hours ago

i used WKWebView highlightr wrapper around highlight.js for syntax highlighting on iOS, and the webview was the biggest memory line in the app

mmis1000

3 hours ago

i mean webKit never handle viewport well when compare to firefox or chrome. it's willing to materialize a 10000*10000 texture when firefox and chrome will think that is too dumb and only load the visible part. It's not a good target if you want to compare windows and mac software quality.

rahulmax

6 hours ago

"Windows users are fundamentally willing to put up with more bullshit than MacOS or Linux users."

I read this circa 2010 and it stuck with me ever since. Also, have felt this way over the years, when I see Windows users work.

SBArbeit

5 hours ago

Super interesting; it's been exactly the opposite in my experience. MacOS/iOS users put up with whatever Apple is telling them they should love - Liquid Glass, right? App Store restrictions, right? Lousy AI, right? - whether it's true or not. Linux users are willing to put up with any amount of work - i.e. bullshit - to make their installations work just to get a UX that's almost as good as Windows from 20 years ago.

As for Windows, I like living in cities. If you live in a city long enough - at least through a couple of major macroeconomic cycles - you'll see it improve in some ways and some neighborhoods, get worse in some ways and some neighborhoods, then improve again, etc. Cycles. Windows found itself in a downturn the last few years, primarily due to the org structure that took Windows shell away from people who could really look after it, and, yes some of those execs have earned my permanent scorn, like a bad local politician would. Now there's a focused team making that neighborhood better. I'm here for the whole ride.

I'll use Linux on computers I don't have to log into very much, so I don't have that UX problem (case-sensitive command lines? Seriously? The 1970's called...). I'll never move to MacOS City; it's like wanting to live in The Villages. Manicured lawns with no soul.

So I live in Windows Town, it's not perfect, no city is, but it's always changing, always moving, going through ups and downs, and now it has a new "city council" that's making changes for the better. And I'm expert enough to make it great for me, and avoid the "neighborhoods" that suck.

This article highlights a problem that Windows has right now, and one which I agree with, which is shipping web apps instead of native. For now, I have a workaround for it:

1. Install uBlock Origin in Edge. 2. Start Edge, browse to MSN Weather. 3. Click the "Add an Application" button in the address bar so I have a Start Menu icon for the page. 4. Delete the in-box Weather app icon.

Now I have the same weather site, no ads, running in about 130MB of RAM.

Enjoy your choice of operating system. Live where you want. Sometimes your city has problems. Move if you want, but don't think you've permanently solved your UX issues if you do, you've just swapped them for different ones.

torh

4 hours ago

> to make their installations work just to get a UX that's almost as good as Windows from 20 years ago

To be fair, that was the peak of Windows UI. Also, KDE Plasma is way ahead of Windows (any of them).

preg_match

4 hours ago

I agree, KDE Plasma runs circles around every UX available now or at any time in the past. And it's not even close.

I've tried using MacOS, and there are so many frustrating things you just have to put up with. Windows is much worse, but to be fair Windows was okay at one point. KDE is, out of the box, seamless, sensible, fast, and unbelievably feature-packed. But even if the default experience isn't your taste, it's trivial to customize it to work however you want. Whatever panels you want, where ever you want, with whatever widgets you want. WYSIWYG with point-and-click. And the windows, too. Window rules, KWin scripts (which are actually full-blown plugins), whatever you want. I want Steam to always open full screen on start up on my second monitor on the third desktop? Sure, I can do that, again point-and-click.

I truly cannot sign the praises of KDE enough. I think everyone who dislikes KDE has probably not delved deep enough. I can recreate the entire GNOME desktop in KDE in an hour. I can recreate MacOS in 30 minutes.

keicwifjwud

5 hours ago

> Liquid Glass, right? App Store restrictions, right? Lousy AI, right?

Liquid Glass needs a lot of cleaning up but it’s fine. App Store restrictions mean very little for iOS users in general and next to nothing for Mac users. Lousy AI also means little to nothing on Mac and earns at max a shrug on iOS—you even have a handy little button to disable all Apple Intelligence shenanigans altogether which is something no Windows user can easily do with Copilot.

No, Apple users are most definitely not having to deal with the same level of bullshit Microsoft’s users are. And it’s not even close.

rstat1

5 hours ago

>> Linux users are willing to put up with any amount of work - i.e. bullshit - to make their installations work just to get a UX that's almost as good as Windows from 20 years ago

I put in the exact same amount of effort to install a Linux distro on my laptop that I would have to install Windows.

1. Download the ISO 2. Write to a USB drive 3. Reboot 4. Run the installer. 5. ??? 6. Profit

And all for an experience with way less bloat, none of the bundled spyware, more consistent UI design (depending on which desktop you're using), and better perceived performance.

>>This article highlights a problem that Windows has right now, and one which I agree with, which is shipping web apps instead of native. For now, I have a workaround for it:

This is still a web app, it doesn't solve the problem of MS being too lazy or cheap to make real desktop apps for things. I mean this is the same company who thought taking the Start Menu of all things and re-making it with web crap was a good idea.

shooly

5 hours ago

I mean, if the only things you can name are Liquid Glass, App Store and not-so-intelligent AI then it seems like Apple users are actually doing quite well?

It's impossible for every idea to be a hit. Liquid Glass was a miss and they backtracked on some changes and fixed some issues that people were vocal about.

SBArbeit

5 hours ago

I can name lots of things I can't stand about MacOS and iOS and Apple hardware, but that wasn't the point of the comment. Some of the things I can't stand about Apple are things that people used to Apple's stuff don't mind. Cool for you. But I'm still not moving to The Villages, ever.

shooly

4 hours ago

> things that people used to Apple's stuff don't mind

... but that's what you said about Windows:

> Windows found itself in a downturn the last few years

> I live in Windows Town, it's not perfect, no city is

> [...] avoid the "neighborhoods" that suck

Really the original comment just reads like you wanted to rant about Apple users and MacOS and that's it. You didn't really give any strong arguments for why Windows is better than MacOS - and "it's not perfect" is not an argument when in the same post you say the exact same about your preferred OS.

baist0

4 hours ago

It's called a "monopoly."

As always, Captain Obvious is quick to respond.

calini

6 hours ago

The Weather app in Windows is more ads than weather, so it checks out.

i-e-b

6 hours ago

The complete works of Shakespeare are about 6MiB. I hate that 100MiB is considered efficient for telling me if it's going to rain later.

3dedb728-3f77

3 hours ago

What if we make all these apps obsolete with < 1mb options.

100 tools < 100mb.

dietr1ch

6 hours ago

At some point you just got to be amazed at it and celebrate.

rdedev

6 hours ago

How much does rainmeter take? I used to load tons of widgets on it in my old laptop. Ahh those were the days

Wowfunhappy

7 hours ago

...you know, I keep reading all this stuff about memory prices, and it does suck, but memory is still much cheaper per gigabyte than it was ~15 years ago.

Which matters because the things most consumers are doing on their computers haven't changed in the past 15 years. We browse the web, edit photos, message friends, and so on. AI generally runs on remote servers anyway.

For years, everyone kept saying it was fine that Electron used gigabytes of memory, because on modern PCs memory was plentiful anyway. Well, it's not plentiful anymore! Maybe it's time software developers actually used resources efficiently?

Hey, you even have an LLM to help you now!

AnotherGoodName

7 hours ago

But it's literally not cheaper than it was ~15 years ago? Right now RAM is the same price per GB as it was in 2007 and prices per GB look to continue to rise.

https://www.tomshardware.com/pc-components/ram/scientist-say...

ttoinou

6 hours ago

Nobody would like to use DDR3 right now though, you can get cheap DDR3 DDR2 if you want some

gruez

6 hours ago

>Right now RAM is the same price per GB as it was in 2007 and prices per GB look to continue to rise.

...when looking at nominal prices (ie. not adjusted for inflation). If you adjust for that the furthest back you can go to get that price is 2011. What's more is that because RAM prices are subject to boom and bust cycles, that price has also been reached in 2015. So just by tweaking two parameters we went from 19 years (2007) to 11 years (2015).

adrian_b

6 hours ago

That is correct, DDR5 today is in real US$ slightly cheaper than DRAM was in 2011, 15 years ago.

For more than 15 years in the past, the price in real US$ of DRAM per GB was always higher than today.

During 2014, there was a brief price peak when DDR3 (the standard current then) was slightly more expensive than DDR5 is today.

Still, the fact that now the price per GB is the same as 15 years ago, is bad enough, and it can still become worse.

Dylan16807

6 hours ago

We had modern programming toolkits that traded some efficiency for ease of use 20 years ago, along with GPU compositing for maximum smoothness. And that's when Vista came out requiring a whole 1GB to run properly. And other than doubling for 64GB that didn't change through 7, 8, 8.1, 10.

Electron was never a great idea but more and more basic things keep moving to it and the result is a disaster. When you use it for several little things at once it turns from annoying waste into massive waste.

baist0

4 hours ago

moder engineers.

kasabali

7 hours ago

15 years ago 4GB was comfortable and 8GB was abundant.

Today 8GB is bare minimum.

drnick1

26 minutes ago

The sad thing is that usability of computers has not improved. More RAM has bought us absolutely nothing when it comes to UI/UX.

Wowfunhappy

3 hours ago

Exactly, isn't that nuts? Especially when we're now paying 15-years-ago prices per gigabyte. What are we getting for that additional space?

hinkley

6 hours ago

But we went from 1080p monitors to 5k monitors and so we are pushing 7x the number of pixels and at roughly twice the bits per pixel.

Wowfunhappy

6 hours ago

True, but I don't really think that accounts for the increase in memory usage.

hinkley

5 hours ago

No but it's the biggest one that's easy to forget.

Feature factory work increases the surface area of every API you touch, and the proliferation of pre-written APIs expands the number of APIs you touch. The combination of the two is not quite O(n²) but the exponent is more than 1, so it's still geometric.

baist0

4 hours ago

You are destroying the subtle mechanism of corporate enrichment.

UltraSane

2 hours ago

I have 64GB of DDR5 Ram and a 64GB pagefile on a pcie 5 SSD and window 11 still runs like crap.

pharos92

3 hours ago

I likely unfairly judge (at a high-level) code security based on how much system resources applications waste. If your app, or OS uses that much resource to perform simple operations then you clearly lack understanding of what the code is doing. How then can I expect it to be secure?

undebuggable

5 hours ago

An app which could have been a website.

Scharkenberg

an hour ago

It is literally the MSN Weather website packaged as a WebView2 app.

superjan

5 hours ago

I don’t know if this is sarcastic. A lot of bloat in GUI apps is because they are built as websites with a bloated front end, dependencies, custom fonts plus the binary compiled code and the decompressed images cached by the browser.

perching_aix

5 hours ago

Is it not?

> Instead, it is essentially an MSN Weather web app built on Microsoft's WebView2 framework. Task Manager shows multiple Chromium-based subprocesses running simultaneously, which contributes to the unusually high RAM usage.

baist0

5 hours ago

This is what traditions mean!

pixel_popping

5 hours ago

Anything above 50MB RAM for this is shameful imo and reflect poor engineering.

trashface

6 hours ago

I'm sure the memory pages compress well /s