Well, for example, Apple Weather has several different animations that are displayed behind the temperature for various weather conditions, such as rain, window, and snow, and those will need to be hi-DPI animations.
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?
Our storage can transfer Gigabytes of data, do hundred thousand operations every second. The hardware is more than capable. If your software stutter when streaming few hundred KBs of data, it's on you.
Why, though? You need some icons and some map imagery, not 4K texture maps
Well, for example, Apple Weather has several different animations that are displayed behind the temperature for various weather conditions, such as rain, window, and snow, and those will need to be hi-DPI animations.
Its 2026. You need 4k assets for job security.
Should be able to get by with using system graphics
For a weather app, you should be able to get by with a couple base vectors you modify based on conditions.
On disk yeah, sure. But you're gonna render them into a pixel buffer which lives in memory.
How did applications do it before? Like in the 90s or 00s
13 replies →
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?
Even if the app is no longer using that memory it is not released until Windows thinks another app needs it.
And then people complain about how unresponsive applications are, all these little stutters as things pop in.
Our storage can transfer Gigabytes of data, do hundred thousand operations every second. The hardware is more than capable. If your software stutter when streaming few hundred KBs of data, it's on you.
1 reply →