see also: progressive enhancement
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
any practical recommendation on how to do that efficiently and effectively (maybe not by hand)?
-
progressive enhancement works but how would you hydrate an app partially and in "small doses"? Would you mainly use events and observers to decide when to hydrate?
End of conversation
New conversation -
-
-
Maybe progressive rendering is a better way to tackle this. At least that’s what makes most sense to me. A delayed but smooth animation (iOS does this) is better than a janky one. ⇒ A delayed but interactive render is better than FID.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How about a worker ? I'm currently multi-threading my application and shipped all business logic and long running tasks into dedicated workers. Processing and rendering approx 3000 messages before take about 10 to 15s now it's down to 1-2s all without locking up the main thread.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well actually I don't know if that would matter or help as much in the case of SSR but certainly long running tasks it has greatly benefited me.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
This is what First Input Delay (FID) looks like.
The page looks ready, but the main thread is busy, so the browser can’t respond to my clicks.
FID approximates this by measuring the time between the first user interaction w/ page & when the browser actually responds.