Comment by iamcoder18

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

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.

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

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

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

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

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

      9 replies →

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

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

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

  • 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. :)

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.