> it seems like devs just assume that people only use their app
It's the "people have powerful computers now so we can be as lazy as we want" culture. We have amazing computers but they feel less powerful than an 80s arcade machine.
It's the "people have powerful computers now so we can be as lazy as we want" culture. We have amazing computers but they feel less powerful than an 80s arcade machine.
This is something I find myself asking more and more almost every time I use a computer or mobile device. I have multiple cores here. Why is anything stuttering? Why are these processes taking so much memory up? Why is this web page pulling down 100MB of traffic? Why do I remember text console DOS apps being so much more responsive than today's click-then-wait UI apps? Before spinning hard drives dropped out of fashion, you could hear that thing grinding away, doing who knows what, while the computer was sitting there supposedly idle! What gives software developers the idea that they can just have their software just wake up and do things without the user commanding it?
Just a particularly egregious example: If there's one thing that nothing on the entire system should preempt, it's the mouse cursor. If I move the mouse, the cursor should move instantly. There is nothing more important that the computer should be doing. I thought this was like a basic, very well understood rule and a solved problem. Hell, I recall a long time ago things like mouse cursor drawing were driven off a hardware interrupt. On today's "modern" computers, if I have a lot of applications running in the background, the mouse cursor will stutter and lag, and text input will be buffered and show up N seconds after I type. Totally unacceptable, yet software continues to ship like this.
EDIT: Sorry, the rant kind of drifted off of the "nobody cares about bloat" problem and into the general "nobody cares about performance" problem.
Sounds like your screenshots are being conveniently uploaded to MS servers so you could share them (Yay!).
Getting such enormous delays when performing otherwise simple operations usually means that network requests are being made, and servers aren't normally snappy when it comes to free storage.
Here is my example of enormous loading times: it takes a few minutes to clear browsing history on the android version of Chrome browser. Quite outrageous.
(also why is everyone so needy these days, to the point of a simple OS-built-in calculator app asking for a rating?)
Some oxygen waster's salary and career is tied to these metrics.
I suspect that it's he heavyweight GUI library that takes a lot of time to initialize.
I would expect to just write it to disk and sync whenever. Instead it seems to take seconds any time it hits “the cloud” and makes me wait. So I bet your screencap tried to transfer your file.
I see this when trying to open files from OneDrive even though I have it local. Word will take seconds to “browse” through online OneDrive directories even though I have them local. So it might take 10 seconds just to pick a folder to save a file.
And of course, afterwards my cpu will peg for minutes doing something.
Windows 2000 on the Pentium 3 with 300 MHz felt way snappier.
The Linux desktop isn't perfect, but basic stuff like that works way better there on the same machine.
obviously, that's just a guess.
It's been like that since Win7.
Not latest iPhone = poor, right?
For example, Facebook ("lite") and google ("go") already optimize their apps to those markets. Why not eg McDonalds?
Oy. I meant "developer time is more expensive than machine time." It's been a long day.