069: With Mike Taylor

59:03   Download

This week we were joined by Mike Taylor, a whitespace strategist from Opera. We talked about (roughly in order):


  • 6:37 The W3C added EME Spec (aka DRM for video)

Q & A

  • 19:24 Percentages seem to render different in Opera, what’s the deal? Should I use media queries instead?
  • 23:42 Wouldn’t it be nice to be able to change the default page scroll behavior (for a horizontal scrolling site)?
  • 30:56 Handling fonts (in silk)
  • 37:04 How would you explain javascript closures to a 6 year old, and how do you use them?
  • 46:42 Caching files with .htaccess: what happens when you have files that change frequently?
  • 52:14 How to test post requests from third parties locally?


  • 28:45 Squarespace – Super nice looking websites (new templates!) that you can create right from the browser. Plus, very advanced developer tools. Head over to Squarespace and start your free trial, and use coupon code “shoptalk4” when you order.
  • 48:53 Environments for Humans – The CSS Summit is an online conference focused totally on CSS July 23–25. Three full days of training, advanced topics, and preprocessors. Coupon code SHOPTALK is good for 20% off.

More Mike

  • blackhawkso

    Is it just me or is time jump not working on this episode?

  • Thanks for putting my question on the show guys! I ended up reading more about it and I like how the Ruby community separates their environments into development for local, staging for live testing and production for live. As far as the solutions go, they’re all helpful. I’m using curl from the command line to fake posts in local development. Then testing with real post backs on staging. Yet another time where taking a leaf out of the Ruby way of doing things really helps. I’m thinking all web developers should learn the Rails way of doing things. Even if you just approach with a “take it or leave it” attitude.

  • skpdx

    Thanks for another informative show. But I must finally object to the way that a particular term is sometimes used on this show. That term is “ghetto.”

    The way this term is used both reflects and perpetuates the lack of African-Americans in web design & programming. And the lack of Latinos, and maybe even Jews.

    After all, the derogatory way in which this term is used on the show suggests that the hosts and guest, and perhaps many listeners too, all share a very WASP-ish point of view — a viewpoint oblivious (stunningly oblivious) to the dynamics of race, ethnicity, and white privilege in America.

    Of course, the acronym ‘WASP’ is rarely used nowadays too — because it just doesn’t apply to as many people, situations, or attitudes as it once did. The fact that it applies here just goes to show how anachronistic your use of the term “ghetto” really is.

    Calling it “anachronistic” is perhaps the kindest way to describe the use of the word “ghetto” on the show. One might also call it regressive, or retrograde, or reactionary, …or just plain ignorant, backwards, and racist.

    In any case,your use of the term “ghetto” ought to be considered as a deprecated usage — something to be avoided. Always.