But the content in the image map wouldn't likely end up in high fidelity (labels are usually truncated versions of the image content), right?
-
-
Yep. Time-to-Interactive is the gold standard and JS is TTI kryptonite
-
If talking about JS frameworks, depending on the app, SSR rehydration may take longer than rendering content (not the app shell) client side.
-
And that's related to other comments in the thread: we need to really integrate this way of thinking into the frameworks themselves, so that they can be functional with minimal client-side code.
-
What about WCs? They're basically just <div>s until booted up, with no way to be SSR'd
-
For non-trivial web components (and apps built using web component frameworks) that can result in significant changes to the look and layout of content after the JS loads.
-
Again, TTI is a leveler. If you've got too much script for your WC-based app, it'll be slow too. Less script, less often.
-
Cool slogan.
End of conversation
New conversation -
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.