@Rich_Harris@jedschmidt@matthewcp It’s quite common to renderToString() for bots and liveness probes in order to handle correct status, renderToStream() for everything else.
@tomayac Thanks for that! It was my first proper conference talk, and was so stressful that I didn’t enjoy it at the time. Now it’s a career highlight 😂
Hydration:
- seamless hydration or render with single render() function
- multiple hydration roots in same container
- automatic recovery from hydration errors
- lazy-hydration with hydrate:idle and hydrate:visible
https://t.co/2iGqTnPsQt
- 7x faster than lit-labs/ssr
- full HTML support (<html>, <head>, etc)
- async expressions
- optional hydration metadata
- WC rendering of light & shadow DOM
- WC rendering with innerHTML
- streaming render in ServiceWorker
Unfortunately, I won’t be able to continue working on the new version of https://t.co/ofROMAPq4A, but it’s in good hands.
I did manage to finish a new implementation of my lit-html server renderer though: https://t.co/2iGqTnPsQt (7x faster than the other guy!)
- (2020-2022) helped build new Samsung Tizen streaming video app as a web-component based SPA, with list virtualization, focus management, spatial navigation, and more (https://t.co/WEr6q1VIhb - Chrome, 1920x1080, arrow keys to navigate)