Corner Office: Know the Code
Why is that better than what everyone is doing now, where you've got your mobile website, your browser site—that works pretty well for people.
That's what's generally referred to as an adaptive approach. Adaptive and responsive are two counterpoints …. [and] there's a couple of reasons why I feel responsive is better. One of them is obviously the efficiency—there's one document that you have to publish, you are managing less code, so for a publisher trying to be more efficient over time, managing less code helps to reduce context-switching.
There are just fewer things you have to do. If you want to deploy some new thing you only have to build it once rather than twice. The other thing about responsive design that's really good is it provides a much better continuity of experience. If you go to the website and you see something, unless you've explicitly hidden it you're going to find it on [every other related] site. It may look a little bit different but the branding's all going to be there, it's going to be relatively consistent and you can reuse a lot of code to [achieve] that.
Apps vs HTML5: A Worthy Debate?
So do you believe the move toward HTML5 will get publishing away from the 'walled garden' quality of proprietary apps?
I believe that they're both important. I don't believe in the apps vs HTML5 debate; I think that there's room for both. Religious wars over code are bad in general. Most technologies have a place in the world and a place that works really well, so tablet editions are a great use of the app form for people who want to do that kind of stuff. For us it doesn't make as much sense, being a technology publication where the content moves so quickly. The other thing we're looking for is volume, and in many cases what you lose with the walled garden is the network effect that gets your content out there, gets you eyeballs. …