3 ms·
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 100M
by kevincox 2mo 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 2mo agoA 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.
- satvikpendem 2mo agohttps://wttr.in/ https://wttr.in/ shows it's very possible.
- kalleboo 2mo agoThe display on that page is literally broken for me, the boxes are all misaligned. It seems like it can't handle Japanese text correctly. Properly working localization in dozens of languages is one of those things that adds "bloat" to modern software that was missing in the bad old days.
- satvikpendem 2mo agoUnicode doesn't require 100s of megs.
- galad87 2mo agoApple'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.
- useasvg 2mo agoUse an svg. Or render everything using css, 100mb is someone not trying. 1gb is absurd abuse that only domestic violence victims put up with.
- qlm 2mo agoQuite a tasteless metaphor, no?
- preg_match 2mo agoSVG is an on-disk format. It has to be rasterized, otherwise how do you have pixels? Each pixel takes up memory.
- anthk 2mo agoVector icons. It can be fit under 50MBs.
- pixelesque 2mo agoThose still have to be rasterised to a pixel-based frame buffer at render/compositing time.
- charleslmunger 2mo agoYes but that space would have existed anyway for a window of that size regardless of its contents.
- puzzleincomplet 2mo ago[dead]
- Dylan16807 2mo agoIf 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.