Episode 69

069 JSJ The Application Cache with Jake Archibald


August 2nd, 2013

51 mins 25 secs

Your Hosts
Special Guest

About this Episode


Jake Archibald (twitter github blog)
Jamison Dance (twitter github blog)
Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up)

01:14 - Jake Archibald Introduction

Works on Developer Relations on the Google Chrome Team

01:57 - The Application Cache

Eric Bidelman: A Beginner's Guide to Using the Application Cache - HTML5 Rocks
Down Fall

07:12 - Working with Single Page Apps
08:40 - Detecting Connectivity

Yehuda Katz: Extend the Web Forward

15:42 - Running Offline
19:55 - Generating Manifest Files

Grunt Task for App Cache Manifests

26:34 - NavigationController
28:49 - Progressive Enhancement

Jake Archibald: Progressive enhancement is still Important
059 JSJ jQuery Mobile with Todd Parker
058 JSJ Building Accessible Websites with Brian Hogan
Feature Detection


Arduino (Jamison)
Draft (Jamison)
RoboRally (Chuck)
Adobe Audition CS6 (Chuck)
Blue Microphones Yeti USB Microphone - Silver Edition (Chuck)
async-generators (Jake)
Rick Byers: DevTools just got a cool new feature in Chrome canary (Jake)
johnny-five (Jamison)

Next Week
Book Club: JavaScript Allongé with Reginald Braithwaite

CHUCK:  Maybe we’ll just talk about your general smarty-pants-ness.

[Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.] 

[This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.] 

[This podcast is sponsored by JetBrains, makers of WebStorm. Whether you’re working with Node.js or building the front end of your web application, WebStorm is the tool for you. It has great code quality and code exploration tools and works with HTML5, Node, TypeScript, CoffeeScript, Harmony, LESS, Sass, Jade, JSLint, JSHint, and the Google Closure Compiler. Check it out at JetBrains.com/WebStorm.]

CHUCK:  Hey everybody and welcome to Episode 69 the JavaScript Jabber Show. This week on our panel we have Jamison Dance.

JAMISON:  Hello friends.

CHUCK:  I’m Charles Max Wood from DevChat.TV. And we have a special guest and that is Jake Archibald.

JAKE:  Hello.

CHUCK:  Jake, do you want to introduce yourself for the folks who haven’t heard of you before?

JAKE:  Sure thing. I work on the Google Chrome team as part of DevRel. What I’m doing there is a combination of speaking at conferences about particular stuff. I got to do a lot in performance at the moment, but I also do a lot of standards work where I’ve done a lot with an alternative to application cache, which we’ll be talking about, but also looking at things like script loading and some of the resource priority stuff.

CHUCK:  Cool. So it sounds like you’re smart on a number of levels then.

JAKE:  Or dumb at all. [Chuckles] I can only see what I work on. I don’t know if I’m any good at it.


CHUCK:  So we brought you on to talk about the application cache. I’m not completely sure I know what is totally involved there. Is it just the cache like you clear the browser cache cache or is it something else?

JAKE:  Well. the aim for the application cache was to let you make a site that works offline. So we’ve got the http cache and that works, in a manner of speaking. But if you have, say a website where you’ve cached your JavaScript, you’ve cached your CSS. You’ve cached your html page and some images. That’s great, but the user will visit another website and the browser will go and delete the CSS file from your site from the cache just to make room for the stuff from this other site. That means that if we were just going to use the http cache for making things work offline, people go to your site, your html’s there, your images are there, your JavaScript’s there, but your CSS is not and that’s going to break your site.