 Hey, everybody, what's up? It's Rob Dodson. Welcome back to day two of the Chrome Dev Summit. I'm joined here by Jeffrey Posnick. Jeff is a member of the Chrome Developer Relations Team. Jeff, you just gave a talk on service worker libraries, past, present, future, et cetera. So for folks out there who haven't seen the talk yet, what are some of the service worker tools that they can use today? Sure. So I spent some of my talk introducing or reintroducing two libraries, SW Precache and SW Toolbox. So those libraries really help with a lot of production-ready scenarios that we see developers facing. SW Precache is great for taking all the static assets in your site and pre-caching them, versioning them properly, making sure the things you need for your application shell is always there. SW Toolbox is great for your runtime strategy. So large images that get cached as you go but aren't going to be pre-cached. You could use SW Toolbox for that, but the nice thing is it'll also handle your cache expiration. So if you have some big image that was used a month ago for an article page, you don't have to worry about that sticking around in your cache forever. And then you also touched on some future tools, like future direction for some of these libraries. And so where are you thinking of heading with some of these things? Sure. So we have these existing tools. They're great, but it's 2016. Some of these tools have been around for a couple of years. We thought, what would things look like if we were developing from scratch using the best practices that people follow today? And we're really trying to go to a more modular approach with our service worker libraries. We want to publish things as standalone modules that could be pulled in as ES2015 imports and really have the same functionality. We don't want this to be a step backwards for folks. We know there are a lot of people who use this in production and are happy with it. But we wanted to make it so that if you wanted to just pick and choose little bits of the library to use, just use the cache expiration, we wanted that to work. And yeah, that's the general philosophy that we're taking. So it's pretty early on in the design stage. We've pushed out really early alpha releases. And we're really interested to see how people use it. So for folks out there who are interested in this and want to get rolling, what is one or one or two resources where they could get started? Yeah, I think we'll hopefully have some links to these. But we have a really great new landing page for all our production current service worker libraries, SWP Cache, XW Toolbox. It's a great resource with a bunch of videos and documentation and articles there. And we're also really interested in collecting feedback from the developer community about the new stuff that we've been building. So there's a GitHub issue that we've opened up where we're asking people to take a look at our proposals, take a look at some of the samples we look like, and just give us feedback. Let us know what you think. Cool, awesome. So we can link to those down in the show notes. And if you haven't done so yet, definitely go check out Jeff's session. Jeff, thank you so much for being with us today. Thank you all so much for watching. Stay tuned for more content from day two of Chrome Dev Summit. Do ya? Cool.