It is certainly aesthetically displeasing for such a relatively simple product to be slow, but it often makes business sense that it's not a top priority.
It is certainly aesthetically displeasing for such a relatively simple product to be slow, but it often makes business sense that it's not a top priority.
The real problem is just the general practice of how software is developed now. If we lived in a world where software development was sane, it would be possible to prioritize speed of development and cut some corners to ship faster, and get a result that is somewhat slower but not ten whole seconds to start up slow.
I watch her screen sometimes to see the differences in our workflows. It is incredible the high latencies and low speeds she has come to view as acceptable in application performance. 2-3 seconds to toggle a menu that’s toggled 30 times in a day; 4 seconds for a small file list update that is performed regularly; tabs in Edge frequently hanging; on and on this goes.
Just sad, really, especially when we have a half gig connection going both ways. The work being performed (and the features designed to do it) should not be seen as resource heavy… because it isn’t. It’s the same exact bs that was done on computers in corporate settings 20 years ago. We’ve added collaborative editing and auto save as defaults - that’s the extent of the difference.
How did we get here?