# SitePoint播客＃124：iPhone贪婪的声音

Episode 124 of The SitePoint Podcast is now available! This week the panel is made up of regular members Louis Simoneau (@rssaddict), Patrick O’Keefe (@ifroggy) and Stephan Segraves (@ssegraves). The panel discuss topics from Google’s new Page Speed service currently in beta to Apple’s IiPhone ruling the Mile High WiFi club.

SitePoint Podcast的第124集现已发布！ 这个小组由常规成员Louis Simoneau( @rssaddict )，Patrick O'Keefe( @ifroggy )和Stephan Segraves( @ssegraves )组成。 小组讨论了Google新的Page Speed服务的主题，该服务目前处于测试阶段，而Apple IiPhone裁决Mile High WiFi俱乐部为​​Beta。

• SitePoint Podcast #124: The iPhone Snooty Voice (MP3, 26:06, 24.0MB)

SitePoint播客＃124：iPhone 贪婪的 声音 (MP3，26:06，24.0MB)

## 剧集摘要 (Episode Summary)

Here are the topics covered in this episode:

Browse the full list of links referenced in the show at http://delicious.com/sitepointpodcast/124.

## 面试成绩单 (Interview Transcript)

Louis: Hello and welcome to another episode of the SitePoint Podcast. We’re back with the panel show, not quite a full panel though, Brad is not with us this week, apparently there are heavy storms in his area so he’s got all his electronics shut off, which I guess is a very wise and cautious thing to do.

Patrick: Too cautious.

Louis: But we do have Patrick and Stephan, hi Patrick.

Patrick: Hey, Louis, good to have you back.

Louis: It’s good to be back. And hi, Stephan.

Stephan: How you doing, Louis?

Louis: I am doing awesome, it’s been good having a bit of a vacation, I was on the show last week, I did a bit of an interview, but it’s good to be back with the panel to talk about some news.

Patrick: I’m sure it was relaxing not to have to hear our voices every two weeks for a little while.

Louis: (Laughter) Ah, yeah, well.

Stephan: He’s like I don’t want to get into that.

Patrick: There’s no denying it, notice how he didn’t say oh that’s not true, he just, yeah, okay good.

Louis: No, seriously, it is really good to chat with you guys again. Kevin was on the show while I was away, that must have been fun as well.

Patrick: It was, yeah. Kevin Yank, one of the original four hosts on the first episode of the SitePoint Podcast was back as a guest host, and I believe Stephan was away for that one, right, Stephan?

Patrick: Yeah, so it was just me and Brad and Kevin, but it was a good time, it was good to have him back on for the first time since he left the show and brought us Louis.

Louis: Cool. Alright, so there are a couple of interesting stories we wanted to talk about this week, we were just talking about it a bit before the show, and we kind of zoned in on some of the same news this week. So, Patrick, do you want to just kick in to the first one?

Louis: Yeah, it’s pretty out there. It almost sound like it would be one of those April Fool’s things if it wasn’t published on July 29th.

Patrick: It’s one of those July Fool’s things.

Louis: Yeah, apparently. They’ve done this sort of thing before, they had the mod page speed Apache module which sort of does a lot of this stuff that you can just install on your server, which sort of makes sense, I can see that, but then going out and making it an actual service where all your files are delivered through Google seems a little bit weird.

Patrick: But then who has faster servers than Google, right?

Louis: Yeah, I do see a point, and I see that if you’re a big company and you don’t want to get in there and start rewriting all your stuff and you just want it to go faster and pay someone else to make it go faster, I can definitely see the appeal of it.

Patrick: So, Stephan, are speed issues a problem with Badice.com.

Stephan: No, I don’t get that traffic; I’m not that big yet. But it’s a cool service, it sounds cool, but it doesn’t really explain to me if I’m running say WordPress, how is it going to take my WordPress and rewrite the WordPress code to be optimized? Is it essentially caching everything?

Louis: It’s not caching, my understanding is it’s the same idea as what they do with mod page speed which does a bunch of different things. For example, it will compress and combine all the JavaScript and CSS files, optimize images, it also does like there were some options in Mod Page Speed, remember we talked about it I think it was with Kevin on one of the first shows I was on; some of the stuff they do is crazy, they’ll omit unnecessary attributes, like when you have a checkbox disabled equals disabled, that second disabled isn’t actually necessary, and all browsers will render the same anyway, so you can just cut that out and make the files a little bit smaller. So there’s a lot of stuff like that, just rewriting the actual output in HTML, compressing, combining and optimizing the JavaScript in CSS.

Stephan: Hmm, okay, that sounds cool. It’d be neat to have it; it’d be neat to have it so that it’s spread out across multiple Google servers all over the world. If my website, Patrick, got that much traffic, then yes, I would use the service (laughs).

Patrick: Yeah, you kind of brought up the point I was thinking of. Is it possible for this sort of thing to break your website?

Louis: See, that’s a really good question, I don’t know. I think that you’d have to — I remember in the original release of Mod Page Speed again, I’m going to go back to that, they gave you the defaults which were the sensible things that it could do and it had no risk of breaking your site, and then you had some other options that you could turn on that were potentially riskier things; like compressing JavaScript in theory sounds fine, but sometimes you never know exactly — there’s a lot of moving parts on a big website, right?

Patrick: Right. I mean you could have a database driven website, it’s interfacing with the database, and obviously all the JavaScript, external JavaScript, Ad Network code, etcetera.

Louis: It’s hard to say exactly, I imagine that they’re probably being pretty conservative with what they’re doing in the service, and maybe they also give you a similar set of options as to what you want it to do. Yeah, it’s interesting, I mean I can see that, I don’t know, for me all this performance stuff is so important, and I think a lot of web developers are still at the point where we know it’s important but we don’t always do it right, you know. Like looking at Sitepoint.com, we’re a blog that’s all about — or a site that’s all about teaching web developers how to do the right thing, and when you look at the code there’s so many places that there could be optimizations, combining CSS files and all sorts of things to make it go faster, and it’s just not a priority because we’re busy rolling out new things and trying to develop new sites, and I think that’s probably the case for a lot of sites out there is that this optimization stuff kind of gets pushed back a little bit. And having the opportunity to just sort of pay some money up front and have it all go through Google is interesting.

Patrick: Yeah, and if you want to find out more about what it does or what it doesn’t do there’s a section of their documentation, Rewriters, that kind of goes through the different things that they do with CSS and images and JavaScript and other things, and it’s way above my head, but for anyone interested in that.

Louis: Yeah, it’s definitely worth checking out. I’m looking forward to seeing like once they’ve actually rolled it out as a service and they’re charging for it, I want to know what the pricing’s going to be, first of all; I imagine Google’s pretty clever with this kind of thing, they’re probably going to make it a pricing where people are going to want to use it.

Patrick: Yeah, maybe like is it going to be like an S3 type pricing perhaps?

Louis: Yeah, I imagine something like that, like a minimal charge per request and then for bandwidth and that’ll be it.

Patrick: Yeah. Is this kind of an inadvertent play at S3 in some way do you think?

Louis: Well, it’s hard to say, S3 is not very fast, see that’s the — if you’re serving images off S3, even with CloudFront, like I wouldn’t want to serve large files off of S3 if speed was a top concern, it’s great because it’s cheap but it wouldn’t be my primary go-to for serving files really quickly. It’s good because it’s targeting stuff that Google is good at and not trying to get into other people’s markets, right, because if you look at what Amazon is doing they’re doing a lot of stuff with regards to providing Cloud hosting and services for website owners, and Google rather than competing with that like, oh, we’re going to make an elastic Cloud compute, or whatever, they’ve gone and done something which is really more focused on what they’re good at which is this stuff, which is sort of in contrast with what they’ve been doing lately with Google Plus and Wave and Buzz and all that stuff.

Stephan: It’s just one more way Google’s taking over the Internet. Oh, man, I’m going to get some bad comments about that one.

Louis: (Laughs) but I mean it’s true, because this is taking it on to another level, right, you’re entrusting Google with the complete delivery of your website.

Stephan: Yeah, exactly.

Patrick: And if you view code as intellectual property, in the case of, I don’t know, maybe a web app or something, you’re giving Google access to your code if that means something to you. I don’t know that it really means something to most people who might be interested in this, but I think this is something where I mean let’s look at it from a startup perspective, right, so they have this website I mean versus using something like an S3 or something or just normal kind of web hosting; you’d only have to worry about necessarily writing the greatest code, just signup with Page Speed, it’ll rewrite some of the performance issues for you, maybe not all of them, but I’m not saying to write bad code, but —

Louis: Yeah, I don’t think it would actually help with any kind of backend inefficiencies like if you were doing inefficient database queries or anything like that, you’re still going to get hit by that; this is really just sort of front end optimization.

Patrick: Yes, right. No, yeah, yeah, yeah, yeah. Which, hey, a lot of programmers aren’t necessarily that good with, right? (Laughs)

Louis: Yeah, exactly.

Patrick: But, yeah, it will be interesting to see if any startups start to use a service like this or we hear of one or two, I don’t know, it’s another business for Google to get into, and in some ways I feel like they’re getting more an more spread out, but I guess that’s part of being a conglomerate.

Louis: Yeah, for me I think it might play out more for your sort of established corporate sites that either don’t have the IT infrastructure or don’t have the expertise in-house to do this kind of optimization.

Patrick: Right.

Louis: For them, just paying some money to have their website suddenly go faster is going to be a no brainer.Alright, so that’s that, I had another story, although Stephan, did you have another story you wanted to bring?

Stephan: Yeah, I just got a real quick one. According to a new study, this was on All Things Digital, according to a new study Apple rules the mobile mile high club. Gogo, the in-flight Wi-Fi service, they released their numbers and Android devices make up about 12% of their users, and the iPod Touch accounts for 20% of handheld connections on their flights; the iPhone makes up about 2/3. So, it’s just interesting to me to see who’s using one in-flight Wi-Fi to begin with and what device they’re using to connect. They didn’t really talk about PC’s or Mac’s much or the iPad, that’s included in their computer numbers, but I just thought it was interesting, the Windows phones and the — I think it’s the Windows phone and there are a few others, they’re so small it’s not even — it’s negligible, and the Blackberry accounts for 6% of users. So, just interesting numbers I thought; do you guys use in-flight Wi-Fi?

Louis: We don’t even have in-flight Wi-Fi here, come on (laughter).

Patrick: I’m not sure, I may have been on like two planes that have it in my life, and it’s always pay to play, so I just can’t bring myself to pay $4.95 or$9.95 or $12.95, which is a Gogo non-mobile rate tiers, or even$4.95 or $7.95 which are their mobile tiers, to just go online for a couple hours; I have to shut it off when they order me to anyway, so it’s like I’m just going to sit here and stare at my non-Internet life for a few hours and save my nine bucks. 帕特里克(Patrick)：我不确定，我可能曾经在两架飞机上过这种生活，而且它总是要花钱玩，所以我无法带自己去付$ 4.95或$9.95或$ 12.95，这是Gogo非移动费率等级，或者甚至是他们的移动价位分别为$4.95或$ 7.95，只能上网几个小时； 无论如何，当他们要我下令时，我都必须关闭它，就像我要坐在这里，盯着我的非互联网生活几个小时，省下我的九美元。

Louis: That brings up exactly the point that I was going to make, which is that I think that because this is pay to play that’s what’s skewing it, right, because we know that the actual usage numbers of iPhone and Android aren’t that skewed, so why would it be so different in-flight. And I think it’s because iPhone users are used to paying for stuff all the time (laughter), and the reason they have iPhones it’s like, hey, I got a lot of money, let’s buy an iPhone (laughter).

Stephan: That’s the funniest explanation I’ve heard.

Patrick: I like that voice, it’s like the iPhone snooty voice (laughter).

Louis: But, no, seriously I’m going to explain it to that because Android makes up more than 12% of Smartphones in the U.S. so what’s going to account for this skew in-flight, is it that Android users don’t even fly, that doesn’t even make any sense. So I’m going to go with Android users are like whatever, I’ve got Angry Birds, I’ll just play that, I don’t need to go online (laughter), $7.95, what are you kidding me? 路易斯：但是，不，我要认真地解释一下，因为Android在美国智能手机中所占比例超过12％，因此，这种机上偏斜的原因是Android用户甚至没有飞，那甚至没有任何意义。 所以我要和Android用户一样，我有《愤怒的小鸟》，我会玩，我不需要上网(笑)，7.95美元，你在跟我开什么玩笑？ Stephan: Well, and you have to remember too — 斯蒂芬：恩，你也必须记住- Louis:$3.00 for pretzels!

Louis: Alright, well maybe we can give them a bit of a SitePoint Podcast bump as well.

Stephan: Agreed.

Patrick: Here’s an extra ten dollars, enjoy it. (Laughter)

Louis: Awesome, that looks really cool. Alright, well that’s a wrap for this week; do you guys want to go around the table? We don’t really have a table; I don’t even know why we say that.

Stephan: We have three tables.

Patrick: We have a figurative table we sit around, yes. And I am Patrick O’Keefe of the iFroggy Network, iFroggy.com, on Twitter @ifroggy, i-f-r-o-g-g-y.

Stephan: I’m Stephan Segraves, you can find me on Twitter @ssegraves, and I blog occasionally at Badice.com.

Patrick: Very occasionally.

Theme music by Mike Mella.

Mike Mella的主题音乐。

Thanks for listening! Feel free to let us know how we’re doing, or to continue the discussion, using the comments field below.

• 0
点赞
• 0
评论
• 0
收藏
• 一键三连
• 扫一扫，分享海报

08-15 116
08-09 148

08-12 189
08-08 114
08-12 1574
08-12 164
08-08 59
08-08 422
08-08 191
08-08 92
08-10 458
08-12 142
08-09 173
08-08 101
08-11 243