The most depressing hallmark of computing backslide is visible repaint. I remember when computers got fast enough that you no longer saw intermediate draw results. Then, browsers happened, and web apps, and now all you see, all day, every day, is stutter and repaint.
-
Show this thread
-
What made me think of this was this video: https://www.youtube.com/watch?v=BRE3ryGworI … Here, a user seems overjoyed by the fact that they can launch a bunch of applications "quickly". But all I see on the screen is _extremely_ laggy performance, despite running on one of the faster CPUs ever made.
7 replies 3 retweets 81 likesShow this thread -
Replying to @cmuratori
It looks to me like each app is drawing the most current state it has very quickly, and then the async data requests are all coming back slow. Probably because it's all network requests?
1 reply 0 retweets 2 likes -
Replying to @Lokathor
At least to me, it looked like both. There are several cases of things just popping in that don't look like network things, but then there are things that might be network things, but it doesn't matter either way.
1 reply 0 retweets 3 likes -
Replying to @cmuratori @Lokathor
The point is that all of that data should have been stored locally, and only if it had changed would it be updated "slowly". There is no way, for example, that the user's "recently added albums" covers should need to come from a network request.
1 reply 0 retweets 7 likes -
Replying to @cmuratori
Yeah, more local caching is absolutely better. A wild guess on why the albums are being updated slowly: some sort of DRM license check before you can even use the data on your own drive.
1 reply 0 retweets 0 likes
I'm sure it's all part of the rotten mix :(
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.