81–90 of 616 posts
> 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?
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?
They do. Never forget, Microsoft's goal is to squeeze as much money from you as possible.
Earlier quoted context omitted.
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)
10 MB is ridiculously overbloated. 1 MB or something in that vicinity should be more like it.
> 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?
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.
https://en.wikipedia.org/wiki/Dennis_Fong#/media/File:John_C...
Earlier quoted context omitted.
10 MB is ridiculously overbloated. 1 MB or something in that vicinity should be more like it.
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.
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 opt…
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…
Sometimes, you need to tell the designers NO. Moving background images don't help people figure out what the weather is going to be.
Earlier quoted context omitted.
10 MB is ridiculously overbloated. 1 MB or something in that vicinity should be more like it.
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.
,_May_1997.jpg){kind=link}