3 ms·
> The user clicks, then nothing happens while the app sends a request, and app only updates the DOM after the request completes I've not seen this too often fr
by maccard 4y ago
> The user clicks, then nothing happens while the app sends a request, and app only updates the DOM after the request completes
I've not seen this too often frankly - that tends to result in a "hung" state for a UI where the app appears to not respond. The most frequent issue I've seen is long transition animations (500+ms) to mask network calls, even when they're not necessary.
> Making a faster framework won't fix the ones that are just coded badly. Making a more intelligent framework might.
This x1000