Panel

Benjamin Lupton (twitter github blog)
Jamison Dance (twitter github blog)
Charles Max Wood (twitter github Teach Me To Code Intro to CoffeeScript)
Joe Eames (twitter github blog)

Discussion
01:00 – Benjamin Lupton Introduction and Background

history.js (twitter / github)
Front-end and back-end developer
Based in Australia
Works full-time open-source

03:19 – history.js

HTML5 History API
Hashbang

09:26 – URL appearances

10:32 – Maintaining states

12:23 – (Joe joins the podcast)

12:30 – Framework usage

13:42 – Overriding history.js

17:33 – JavaScript community and evolution

21:10 – Particular problems that history.js is geared toward solving

22:07 – Sites implementing history.js

37signals

25:18 – Other libraries that do the same thing

26:12 – Page reloads

32:14 – Browser limitations

34:37 – Live event in jQuery

35:42 – history.js: a deep or shallow library?

37:43 – Resources for history.js
Picks

booq: Vyper XL2 (Jamison)
Jordan Santell (Jamison)
Star Wars: Red Harvest (Joe)
Nitro Circus: The Movie (Joe)
Arrested Development (Joe)
f.lux (Chuck)
docpad (Benjamin)
Paulo Coelho (Benjamin)

Transcript
BENJAMIN: Anything important, I hear from my wife. So, I could finally have that thing where Facebook doesn’t infiltrate my mind with cat pictures anymore. 

[This episode is presented to you by ComponentOne, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to wijmo.com and check them out.] [Hosting and bandwidth provided by the Blue Box Group. Check them out at bluebox.net]

CHUCK: Hey everybody and welcome to episode 31 of the JavaScript Jabber show. This week on our panel, we have Jamison Dance.

JAMISON: Howdy Doody!

CHUCK: I’m Charles Max Wood from devchat.tv and this week, we have a special guest and that’s Benjamin Lupton.

BENJAMIN: Hello.

CHUCK: He is the author of history.js and why don’t you introduce yourself? Because that’s all I really know about you other than history.js and you are many time zones away.

BENJAMIN: [laughs] Yeah. So, I have been doing JavaScript pretty much my entire life and been doing it professionally since about 2006, full time. And over the time, I’ve developed some open source project. One of them became quite popular and that was History.js it makes HTML5 History API that was compatible with like hashes and things like that. We’ll go into that late. Yeah, that became really popular. Now I other stuff with Node a lot as well.

CHUCK: Ooh. A front end and a back end person.

BENJAMIN: Only because I’m Node.

JAMISON: You are basically like a unicorn.

CHUCK: Yeah.

JAMISON: You are a mystical creature.

CHUCK: You are too well rounded. You are going to put us to shame.

BENJAMIN: Well, it’s easier being with Node.

CHUCK: Yeah, that’s true.

JAMISON: Yeah it’s true. Where do you work?

BENJAMIN: I work for my own company right now. We’ve been doing JavaScript constancy for a few start-ups in Australia. And now, I’m looking at going completely full time with just the open source stuff.

CHUCK: Oh, cool. How do you manage going full time open source?

BENJAMIN: Right now, we’ve got premium support. I’m going with a few companies and we are looking into other options as well.

CHUCK: Right. Yeah. I’m in the same boat with my podcast. I’d love to go full time podcast and less full time consulting.

JAMISON: So the real question is, if I pay you enough money, will you put a gigantic ASCII art picture of my face in the History.js source code?

BENJAMIN: Perhaps.

JAMISON: Okay. We’ll have to talk after.

CHUCK: I’m going to have to figure out how to do that. Let’s see… Image to ASCII art…

BENJAMIN: In podcast.

CHUCK: Yeah and then I’ll…

JAMISON: Oh Chuck, you could do it so there’s face that shows up like in the waveforms on the sounds.

CHUCK: [laughs] I don’t know about that.

PlayPlay

Sponsors

Subscribe by Email