Rendering on the Web: Performance Implications of Application Architecture (Google I/O ’19)

Rendering on the Web: Performance Implications of Application Architecture (Google I/O ’19)


Danny Hutson

14 thoughts on “Rendering on the Web: Performance Implications of Application Architecture (Google I/O ’19)

  1. We dont need server side rendering once lit-HTML is UP. Its for fools who know React with Redux but dont know HTML5, CSS and native functionalities of Javascript. Its for people who learn react for salary hike

  2. Links from the video:
    https://bit.ly/rendering-on-the-web
    https://bit.ly/react-progressive
    https://bit.ly/ng-lazy
    https://bit.ly/vue-lazy
    https://bit.ly/spectrum-ssr
    https://bit.ly/react-partial-hydration

    Warning! Do NOT use the ivy-universal link. It has been hijacked. The https://bit.ly/ng-lazy link leads to the real ivy-universal project.

  3. Nice overview of current techniques for server side rendering. However the whole idea seems like a big hack. I hope that at some point google, ms, apple etc. will say 'enough of this crap, we need some holistic solution and not hack html+js'.

  4. I'm eager to see how Sveltejs shapes up in the future. Out of the box, it supports SSR (Server Side Rendering) and rehydration

Leave a Reply

Your email address will not be published. Required fields are marked *