HTML is the new JSON: Declarative partial updates explained #GoogleIO

But I do want to show you something that I think is just going to change the way that we build some UIs in the future that are both performance and also UI wins. And I think it's one of the biggest changes to HTML in a decade. So, if you go back to my bedroom and look at the clock on my machine, you can see it updating every single second, kind of what you'd expect from a clock. But the thing is like there's no JavaScript on this page. Like it's updating every single second, and [music] that's because of the declarative partial updates that implementation that is coming into Chrome. The clock demo isn't all that useful by itself, but I do think it highlights some compelling potential use cases. So, for example, if you have a huge amount of application structure, say a massive menu, you can render it at the end of your page, let the critical content get rendered first, then you can patch it back into the DOM just a little bit later. It's available in Chrome 148. Now, I want to show you one other thing where I think, you know, I would like to make HTML the new JSON, and we have a new API that's going to help with that. So, if you if you've been using frameworks, you'll probably know about something that's called the island architecture. I think it's a beautiful pattern and it's a beautiful concept, but it's just going to be even easier for us as just like plain JavaScript developers to do something very similar. So, the new streaming API for dynamic markup gives you a revamped way >> [music] >> to improve experiences by letting you inject HTML into documents by the stream HTML >> [music] >> and stream HTML unsafe methods. What this really means is you can take the body from a fetch request and then just stream it directly into the DOM. These APIs have both been available in Chrome since Chrome 148, so pretty recent. They're going to change the way I think, personally, they're going to change the way that we build web experiences well.