21–30 of 601 posts
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.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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.
LumiWeather for AmigaOS runs on 2 MB RAM.
That's also bloated, couldn't they find a better comparison to illustrate the egregious waste?
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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.
Or render everything using css, 100mb is someone not trying. 1gb is absurd abuse that only domestic violence victims put up with.
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?
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.
> 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?
But yeah, I still remember when a weather app would take 10 MB and I was complaining (1999)
Earlier quoted context omitted.
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.
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.