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

One of the core values of the web is its accessibility: the same medium can be used to deliver content that adapts to different devices, capabilities and connection types. This variability needs to be factored into every architectural decision that is made. Luckily, frameworks are here to help.This talk will showcase upcoming framework features that reduce the impact of architectural constraints and potentially improve performance beyond what is possible today.
Watch more #io19 here:
Web at Google I/O 2019 Playlist → goo.gle/io19web
Google I/O 2019 All Sessions Playlist → goo.gle/io19allsessions
Learn more on the I/O Website → google.com/io
Subscribe to the Chrome Developers Channel → goo.gle/ChromeDevs
Get started at → www.google.com/chrome/dev/
Speaker(s): Jason Miller, Houssein Djirdeh
TFE0DD event: Google I/O 2019; re_ty: Publish; fullname: Jason Miller;

[@corymcaboy7509]

I thought this was a rock star talk. So much knowledge is just 30 minutes. Thank you!

[@maxverse]

I watched this video in full while doing research for a presentation at the Recurse Center, and I got so much out of it! It's really thorough and covers all the bases, with super helpful examples from different frameworks. Thank you for all your hard work on this!

[@robertgao9241]

this is sooooo amazing talk ,I just love it

[@doveprince3095]

Great presentation by the duos

[@lucasquinnlife]

thanks nextjs for doing this stuff.

[@UliTroyo]

Great talk! Very crunchy.

[@javiasilis]

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

[@rgfxnet]

Enjoyed the talk, a little heavy on framework dependency.

[@shangruyi5439]

Why we use JS if the html can be rendered as static one? little confusing.

[@dibaliba]

I think what this talk mentioned is finally just adopted by people widely recently.

[@jon_cammisuli]

The bit.ly ivy-universal link is not working. It tries to go to a phishing site. Just an FYI

[@ErnestoNoeIsordiaCuevas]

I'm gonna be fans of Google dev

[@gopalvirtual]

aren't we going in loops, django views -> mvc -> spa -> ssr with hydration -> ssr only (which is basically django pages)

[@rosalinmahalik6311]

Can I get this ppt?

[@AkkayHT228]

0:17 - 0:20 lol that pause

[@corymcaboy7509]

He was probably waiting for the slide to turn.

[@maxverse]

It's great to take a moment to collect your thoughts, reset, and give the audience a moment to do the same!

[@viraj_singh]

22:37 angular trying to keep up.

[@kiddkai]

We are pretty much doing the same thing to push the timelines

[@samirsaeedi74]

So I guess ultimately code splitting is much simpler and effective than SSR.

[@dibaliba]

20:21

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'.

[@pradeepverse]

Audio and video are out of sync :(
Bad UX :D

[@JasonMillerDeveloper]

sorry about that! we're hoping to get it fixed shortly.

[@mpoisot]

Jason Miller still not fixed 3 months later.

[@vsicok2862]

disappoint about ssr, it's ongoing tech, not the future.

[@cgopi24]

Please stop having ping-pong talks. The context switch is hard for the presenters as well as for the audience. It benefits nobody and I don’t know why Google talks are like this.

[@mjarc1]

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