Episode 53 of The SitePoint Podcast is now available! This week your hosts are Stephan Segraves (@ssegraves) and Kevin Yank (@sentience).
SitePoint Podcast的 第53集现已发布！ 本周的主持人是Stephan Segraves( @ssegraves )和Kevin Yank( @sentience )。
You can also download this episode as a standalone MP3 file. Here’s the link:
您也可以将本集下载为独立的MP3文件。 这是链接：
SitePoint Podcast #53: “I’m here with the booze!” (MP3, 48.7MB)
SitePoint Podcast＃53：“我在这里喝酒！” (MP3，48.7MB)
Here are the topics covered in this episode:
以下是本集中介绍的主题：
Full feeds versus partial feeds, and advertising 完全供稿与部分供稿以及广告 Virgin America drops Flash from its home page 维珍美国航空从其主页上删除Flash Google’s Matt Cutts confirms 301 redirects cost PageRank Google的Matt Cutts确认301重定向的费用为PageRank Microsoft releases IE9 developer preview 微软发布IE9开发人员预览版Browse the full list of links referenced in the show at http://delicious.com/sitepointpodcast/53.
浏览http://delicious.com/sitepointpodcast/53中显示的参考链接的完整列表。
Stephan: Evom – Convert and Download Videos to iTunes
Stephan： Evom –将视频转换并下载到iTunes
Kevin: Dynamic Dummy Image Generator
凯文： 动态虚拟图像生成器
Kevin: March 19th, 2010. Full-content feeds generate extra traffic; Google reveals SEO secrets; and Internet Explorer 9 does it all. I’m Kevin Yank and this is the SitePoint Podcast #53: “I’m here with the booze!”
凯文： 2010年3月19日。内容丰富的Feed会产生额外的流量； Google透露SEO机密； Internet Explorer 9可以完成所有操作。 我是Kevin Yank，这是SitePoint播客＃53：“我在这里喝酒！”
And it’s just the two Mac nerds on the show today. Stephan how’s it going?
而这只是今天节目中的两个Mac书呆子。 斯蒂芬过得怎么样？
Stephan: It’s going alright, how about yourself?
史蒂芬：一切都很好，你呢？
Kevin: Pretty good. I think Brad’s got family obligations today, and Patrick is still lost in the maelstrom of South by Southwest. We haven’t heard from him after that yet. He’s yet to put his head above water. I’m sure we’ll be hearing plenty about that … I hesitate to call it a conference, it’s kind of a giant party in Austin.
凯文：很好。 我认为布拉德今天有家庭义务，而帕特里克(Patrick)仍然迷失在西南偏南的漩涡中。 此后我们还没有收到他的消息。 他还没有抬起头来。 我确信我们会听到很多有关此事的信息。。。我毫不犹豫地称它为会议，这在奥斯丁是一个巨大的聚会。
Stephan: It does seem that way sometimes, doesn’t it?
斯蒂芬：有时候看起来是这样，不是吗？
Kevin: But yeah, I’m sure we’ll be hearing all about that from Patrick on a future show. But just the two of us today, I think this is the second time it’s been just the two of us, right Stephan?
凯文：但是，我敢肯定，在以后的演出中，我们会从帕特里克那里听到所有的消息。 但是，今天只是我们两个人，我想这是我们两个人第二次来，对，斯蒂芬？
Stephan: Yeah, second time.
斯蒂芬：是的，第二次。
Kevin: And even though there’s less of us it seems like we end up talking longer. So we’ve got a lot to get through today. We’ve got the Internet Explorer 9 developer preview. I think it’s ironic that it’s the two Mac nerds here to talk about IE9 because short of a virtual machine, neither of us have a machine to install this thing, do we?
凯文：尽管我们的人少了，但看来我们结束了更长的谈话。 因此，我们今天有很多工作要做。 我们已经有了Internet Explorer 9开发人员预览版。 我觉得具有讽刺意味的是，这两个Mac呆子在这里谈论IE9，是因为缺少虚拟机，我们俩都没有机器来安装IE9，对吗？
Stephan: No.
斯蒂芬：不。
Kevin: We’ll come back to what we think about IE 9, even though we can’t really play with it, at the end of the show. But first, being Mac nerds, John Gruber is someone that we both follow pretty closely. His blog, Daring Fireball, talks about Mac news, but also a lot of sort of surrounding tangential issues, and it’s always a great read. And in the past week I noticed he was talking about full- versus partial-content feeds. And I wanted to talk about that a bit today. Stephan, do you have strong feelings about full or partial feeds?
凯文：在节目结束时，我们将回到关于IE 9的想法，即使我们无法真正使用它。 但是首先，作为Mac的书呆子，约翰·格鲁伯(John Gruber)是我们都非常关注的人。 他的博客Daring Fireball谈论Mac新闻，但同时也涉及许多切线问题，而且读起来总是很不错的。 在过去的一周中，我注意到他在谈论完全内容馈送与部分内容馈送。 我今天想谈一点。 史蒂芬(Stephan)，您对全部或部分Feed有强烈的感觉吗？
Stephan: Well, I’ll just say this, I only subscribe to two truncated feeds in my feed reader. All the rest are full feeds, and the two that are truncated are both news feeds. And well there’s a third, I won’t mention who it is because he listens to the show. He’s actually on the show.
史蒂芬：好吧，我只想这么说，我在订阅源阅读器中只订阅了两个截断的订阅源。 其余所有都是完整的提要，被截断的两个都是新闻提要。 还有三分之一，我不会说是谁，因为他听了表演。 他实际上在演出中。
Kevin: Oh, I see. Alright, fair enough. I actually thought I subscribed to more partial feeds then I did. In preparation for this show I went through my RSS reader and just read a day’s worth of posts looking for the first one that would be from a partial feed.
凯文：哦，我明白了。 好吧，很公平。 我实际上以为我订阅了比我更多的部分提要。 在准备这个节目的过程中，我浏览了RSS阅读器，并阅读了一天的信息，寻找第一部分来自部分提要的信息。
For those who aren’t big feed readers in our audience, the idea here is, at least in my feeds, my collection of feeds, most of them are what you call full-text feeds, which means what you get when you’re reading the site in your feed reader is the whole story. If there’s a blog post you can read the whole blog post in your feed reader, and the only reason to click through would be if you wanted to leave a comment or read what other people have written about that post in the comments, or if you wanted to use that post as jumping off point to sort of browse the rest of the site. Often I’ll end up clicking on links in the story which then take me to that site or to other sites. But some sites seem a little reluctant to put out full feeds like that, and so what they provide is a partial feed, which has these truncated posts. Often it’s the first couple of sentences of the post and then it goes dot-dot-dot, click here to read more.
对于那些不是我们的提要阅读器的读者来说，这里的想法至少是在我的提要中，我的提要集合中，其中大多数是您所谓的全文提要，这意味着您在阅读提要阅读器中的网站就是故事的全部。 如果有博客文章，则可以在供稿阅读器中阅读整个博客文章，而单击的唯一原因是您要发表评论，还是要阅读其他人在评论中对该帖子的评论，或者您是否愿意希望将该帖子作为出发点来浏览网站的其余部分。 通常，我最终会单击故事中的链接，然后将我带到该站点或其他站点。 但是有些站点似乎不太愿意提供这样的完整提要，因此它们提供的是部分提要，其中包含这些截断的帖子。 通常，它是帖子的前几句话，然后变成点对点的形式，单击此处以了解更多信息。
And I was all prepared to sit down here and say that I have a lot of patience for these things, and I don’t mind clicking through if they want to make me do that, but looking at my feed reader I think I would have been lying to say that because it took me quite a while to finally find a post that was from a partial feed. The site in question that I subscribe to, their feed for is Macenstein—true to form another Mac feed—but yeah, they have a couple of sentences or so and it just trails off and you have to click through to read the whole story.
我已经准备好坐在这里说我对这些事情有足够的耐心，如果他们想让我这样做，我不介意点击，但是看着我的提要阅读器，我想我会我一直在撒谎，因为我花了相当长的时间才终于找到了一个来自部分提要的帖子。 我订阅的有问题的站点的供稿是Macenstein(确实是另一个Mac供稿)，但是，是的，它们只有几句话 ，而且只是尾随 ，您必须单击以阅读整个故事。
Stephan: Now do you use a feed reader on your iPhone?
斯蒂芬：现在您是否在iPhone上使用供稿阅读器？
Kevin: I do. I use NetNewsWire on my iPhone but I’ll be the first to admit it is the exception that I’ll be reading on my iPhone. That’s pretty rare.
凯文：是的。 我在iPhone上使用NetNewsWire ，但我将第一个承认这是我将在iPhone上阅读的例外。 那是非常罕见的。
Stephan: Okay. Because I read on my iPhone a lot, so I’ll download the morning stories onto my iPhone; and then when I’m somewhere that I can read I’ll read it, offline usually. So for me the full feed makes sense because I can get the whole story I’m looking for rather then a couple sentences of something that may be really interesting. But if I’m on an airplane I want to read the whole thing.
史蒂芬：好的。 因为我在iPhone上阅读很多东西，所以我将早上的故事下载到iPhone上。 然后当我在可以阅读的地方时，通常会离线阅读。 因此，对于我来说，完整的提要很有意义，因为我可以得到我一直在寻找的整个故事，而不是几个可能真的很有趣的句子。 但是，如果我在飞机上，我想阅读全部内容。
Kevin: Right, that is a serious issue. And even if you’re not, even if you’re somewhere where you have 3G coverage, that full feed often provides a far superior reading experience on a mobile device than if you click from the partial feed to the full page and then your phone struggles to download all the ads and the navigation, when all you wanted to do was read the full story.
凯文：对，这是一个严重的问题。 而且即使您不在，即使您位于3G覆盖的地方，与从部分供稿单击到整个页面然后再单击手机相比，完整的供稿通常在移动设备上都可以提供更好的阅读体验当您只想阅读全文时，就很难下载所有广告和导航。
Stephan: Exactly. And I’ve gotten around that with Instapaper and things like that, Read It Later and things like that, but it’s more work then I should have to do. And reading the article, and you can get into it, Kevin, about why they chose to do this, but it’s really about money and getting people to view the pages and I understand that, I mean they’re a business, they’re trying to make money.
史蒂芬：是的 。 我已经使用Instapaper和类似的东西， 稍后阅读和类似的东西解决了这个问题，但这是我必须要做的更多工作。 读完这篇文章后，凯文(Kevin)将会介绍他们为什么选择这样做，但这实际上与金钱有关，并促使人们查看页面，我明白，我的意思是他们是企业，他们是试图赚钱。
Kevin: Right.
凯文：对。
Stephan: So I can sympathize.
史蒂芬：所以我可以同情。
Kevin: So John Gruber took exception to a few sites that, well, he was trying to provide the contrasting point. He said he’d seen a few sites go to partial feeds saying that they make their money from ads on their web pages that you don’t see in the feed, and therefore in order to protect their revenue, their source of revenue, they had to go to the partial feeds force readers to click through to these pages with ads on them. Jason Snell from Macworld.com was saying if only there were some studies out there that prove that full text feeds created more traffic than partial text feeds, then maybe they would be able to justify going back to full text feeds. So John Gruber said well look I can put up my hand as someone who has experimented with this and seen better results from full-text feeds. He says, “During Fireball’s RSS feed, which contains the full content of the site, not only generates money directly but has grown to become the single largest source of revenue for the site.” And reading through his story on that, first of all, he says he’s gone out of his way to source ads specifically for his RSS feed. It seems like a lot of people out there seem to take for granted that ads in RSS feeds have to be crappy, or have to be really generic or simple; in any case, they really don’t pay the bills. But it seems like John Gruber’s out there to prove that if you treat your RSS feed as a first class citizen when it comes to the content that you’re producing and then the ads that you’re going to source for it you really can make some money. And reading his feed, ads in his feed are not little one-liner links at the bottom of every post; he actually posts ads as full stories to his feed. And these ads appear nowhere except in his RSS feed. And I for one find that he attracts really high quality advertisers that are really relevant to readers of his site, and I actually don’t mind reading those ads almost as if they were stories, because generally they are very relevant to me. And they usually take the form of a handwritten testimonial written by John Gruber for whatever product is sponsoring the feed that week.
凯文： 约翰·格鲁伯(John Gruber)例外地访问了一些站点，他试图提供对比点。 他说，他曾见过一些网站访问部分供稿，说它们是通过您在供稿中看不到的网页上的广告赚钱的，因此，为了保护他们的收入，收入来源，必须进入部分供稿，迫使读者点击带有广告的这些页面。 来自Macworld.com的Jason Snell表示，如果仅存在一些研究证明全文摘要比部分全文摘要产生的流量更多，那么也许他们有理由再回到全文摘要。 因此，约翰·格鲁伯(John Gruber)说的很好，我可以举起我的手，因为有人对此进行了试验，并从全文供稿中看到了更好的结果。 他说：“在Fireball的RSS feed中，它包含了网站的全部内容，不仅可以直接赚钱，而且已经成长为该网站最大的单一收入来源。” 首先，通读他的故事，他说他已经竭尽全力为他的RSS feed专门寻找广告。 似乎很多人似乎理所当然地认为RSS提要中的广告必须笨拙，或者必须真正通用或简单。 无论如何，他们真的不付账单。 但是似乎约翰·格鲁伯(John Gruber)在那里证明，如果您将RSS feed视为一流的公民，则涉及到您要制作的内容以及要为其采购的广告，您确实可以制作一些钱。 阅读他的提要，提要中的广告在每个帖子的底部都是不少的单线链接； 他实际上将广告作为完整故事发布到了Feed中。 这些广告除了出现在他的RSS Feed中之外，什么都没有出现。 我发现他吸引了与他的网站读者真正相关的高质量广告商，而且我实际上不介意将这些广告看成是故事，因为通常它们与我非常相关。 他们通常采用约翰·格鲁伯(John Gruber)撰写的手写推荐书的形式，以证明该周赞助饲料的任何产品。
Stephan: Yeah, his ads are really good. I think that’s the way I would do it if I was doing what he was doing. I think it’s the right way to go about advertising in a feed rather then some kind of like gaudy image or link at the bottom, click here. I wouldn’t click. Some of the products he’s actually advertised I’ve gone to the websites; I’ve clicked the link in the ad to see what he was talking about just because it sounded interesting.
斯蒂芬：是的，他的广告非常好。 我认为如果我正在做他正在做的事情，那就是我会这样做的方法。 我认为这是在Feed中投放广告的正确方法，而不是底部的类似艳丽的图片或链接，请点击此处。 我不会点击。 我去过这些网站，他实际上在做广告的一些产品。 我点击了广告中的链接，以查看他在说什么，只是因为它听起来很有趣。
Kevin: And when is the last time you could say that about a web based ad?
凯文：什么时候可以说一次基于网络的广告呢？
Stephan: You know I don’t think I’ve ever clicked on a Google AdWord, you know, that’s been embedded in a feed.
史蒂芬(Stephan)：您知道我认为我从未点击过嵌入在供稿中的Google AdWord。
Kevin: Not on purpose anyway. Have you ever done that? You click it and you go “Aw crap, I just clicked that ad!”
凯文：反正不是故意的。 你做过吗？ 您单击它，然后转到“糟糕，我刚刚单击了该广告！”
Stephan: You hate that, don’t you?
斯蒂芬：你讨厌那个，不是吗？
Kevin: You wonder if they run enough ads, if they make money just off of the accidental clicks sometimes. But I think the takeaway point for me here that I don’t think he makes a big enough deal about is that maybe the reason people aren’t making money off their RSS feeds is because it calls for a different kind of advertising content. And it’s just like it took a lot of arm twisting to get traditional advertising execs to buy into producing ads specifically for banner ad spots on the Web—you know, that took years for them to really treat that as something that they developed ads for commonly—I think RSS feeds might demand that same painful process where you’ve got to show, “Hey look I will develop your ad creative for me if you pay me, and I will guarantee you this much click-throughs”, and if you can show that the ads pay off then maybe you can start convincing these people that RSS ads need to be a new ad format. It’s not just text links; it’s not just banner ads and maybe it is worthwhile.
凯文：您想知道他们是否投放了足够多的广告，有时是否仅因意外点击就赚了钱。 但是，我认为对我而言，我认为他没有做足够大的事情的要点是，人们之所以无法从RSS提要中获利，可能是因为它需要一种不同类型的广告内容。 就像花了很多力气才能让传统的广告主管购买专门为网络上的横幅广告位制作广告一样-您知道，他们花了多年的时间才能真正将其视为他们为通用广告开发的东西“我认为RSS提要可能会要求您经历同样痛苦的过程，“您好，如果您付钱给我，我会为您开发广告素材，并且我会向您保证这么多的点击次数”，如果您可以证明广告获得了回报，那么您也许可以开始说服这些人，使RSS广告成为一种新的广告格式。 不只是文字链接； 这不仅是横幅广告，也许是值得的。
Stephan: Yeah. I agree.
斯蒂芬：是的。 我同意。
Kevin: So Jason Snell from Macworld, the way he seems to interpret John Gruber’s point is that yes there is money to be made in RSS ads as a one man operation, but that this doesn’t scale to bigger operations like Macworld. He says “the economics of a one man blog are vastly different from the economics of a publishing company with multiple products, a staff of editors, and ad sales force, and a development team.” And I wonder, see, it just seems maybe an entity that is as large as Macworld, the problem isn’t that this ad format doesn’t scale to them, it’s that they are all— all of their workflows, all of their processes, all of these people’s jobs revolve around current web based ad formats. And getting that big ship to turn on a dime to try a new ad format to make money off of RSS, the way John Gruber has proven it can be done, is too difficult.
凯文：来自Macworld的Jason Snell， 他似乎解释John Gruber观点的方式是，是的，RSS广告可以单人操作赚钱，但是这并不能扩展到Macworld等更大的业务。 他说：“一个人的博客的经济状况与拥有多种产品的出版公司，编辑人员，广告销售人员以及开发团队的经济状况截然不同。” 而且我想知道，似乎可能是一个与Macworld一样大的实体，问题不在于这种广告格式无法适应它们，而是它们全部—所有工作流，所有流程，所有这些人的工作都是围绕当前基于网络的广告格式展开的。 而且，让约翰·格鲁伯(John Gruber)证明可以做到的方式，让那艘大船打开一角钱尝试一种新的广告格式来从RSS上赚钱，实在太困难了。
Stephan: I don’t think he really addresses the issue. I mean he just kind of says the economics are different, and that’s just kind of the end of it. He doesn’t say why, you know.
史蒂芬：我认为他并没有真正解决这个问题。 我的意思是，他只是说经济有所不同，而这仅仅是结局。 他没有说为什么，你知道。
Kevin: Mm. Yeah.
凯文：嗯。 是的
Stephan: I mean he’s got to have a solid profit margin, okay, well don’t we all? I mean, or we go broke. So if the issue is scale then it seems to me that someone like the example that Gruber was talking about, or one of the examples, is Gawker. If Gawker has all these different blogs, Lifehacker, they’ve got Deadspin, all these different blogs, and they put a lot of content out there, if they came out with some really good ads that they could throw in with the content just like Gruber does, I don’t see any reason it couldn’t scale. That was relevant to what they’re publishing; if it’s a football blog why not put football content in there rather then some Google AdWord, you know? I don’t know.
史蒂芬：我的意思是他必须有可观的利润率，好吧，我们不是吗？ 我的意思是，否则我们破产了。 因此，如果问题是规模问题，那么在我看来，像Gruber谈论的示例或示例之一就是Gawker。 如果Gawker拥有所有这些不同的博客(Lifehacker)，Deadspin和所有这些不同的博客，并且他们在其中放置了很多内容，如果它们发布了一些非常好的广告，它们可以将这些内容与Gruber可以，我看不出它无法扩展的任何原因。 这与他们发布的内容有关； 如果这是一个足球博客，为什么不把足球内容放在那里，而不是一些Google AdWord，您知道吗？ 我不知道。
Kevin: I’ll be the first to say I’m talking out of my butt here, but if I were to try and come up with a theory for why it might not scale, maybe RSS, maybe reading content through feeds is still something that advanced users, power users do. Maybe it’s still a niche thing compared to web browsing. And therefore the largest audience you could possibly capture for your feeds would still be too small to pay a staff of content producers at a company as opposed to… no?
凯文：我将是第一个说我在这里说话的人，但是，如果我尝试提出一种理论，说明为什么它可能无法缩放，也许是RSS，也许是通过提要阅读内容高级用户，高级用户可以做到的。 与网络浏览相比，也许这仍然是一个小众市场。 因此，您可能会为Feed捕获的最大受众仍然太小而无法支付公司的内容制作人员的费用，而不是……不是吗？
Stephan: No, no, I buy into that, I do. Because I think that you look at Gruber’s audience is nerds really, it’s geeks. That’s who reads his blog. Who reads … I’m trying to think of … Deadspin. Wy wife reads Deadspin. And my wife’s geeky, but it’s a football blog. So people who read these blogs aren’t reading them usually through feed readers, they’re just browsing the website and they’ll click on something that interests them. So I can completely see how you’d want to drive the traffic to that particular blog to the website because that’s where most of your audience is anyways.
斯蒂芬：不，不，我同意。 因为我认为您看到Gruber的听众真的是个书呆子，所以很怪胎。 那是谁读他的博客。 谁在读……我想着……Deadspin。 贤妻读《 Deadspin》。 和我妻子的怪异，但这是一个足球博客。 因此，阅读这些博客的人通常不会通过供稿阅读器来阅读它们，他们只是在浏览网站，然后点击感兴趣的内容。 因此，我可以完全看到您希望如何将访问该特定博客的流量吸引到该网站，因为无论如何，这是大多数观众所关注的地方。
Kevin: Okay, where’s the downside, then, is my question. So you mentioned Gawker, and I suppose Gawker was once a very nerd, very geeky sort of site, and is trying to break into the mainstream at this point. And they have just switched from full-text feeds to partial feeds. Their quote from Nick Denton from Gawker, he says, “Gawker Media is an ad-supported company. RSS ads have never realized their potential. At the same time we sell plenty of ads on our website. So yes, it is in our interest for people to click through if enticed by an excerpt.” But if what you’re saying, Stephan, is true, if the mainstream audience haven’t figured out feeds or maybe they just will never read content that way, what is the downside for a mainstream site to offering full-text feeds? If their mainstream audience is going to come to their site and see their ads anyway, who is reading your full text feeds? You’re not cannibalizing from your mainstream audience; what you’re doing is providing something just for the small segment of nerds in your audience.
凯文：好的，那是我的问题。 所以您提到了Gawker，我想Gawker曾经是一个非常呆板，怪异的网站，并且现在正试图成为主流。 他们刚刚从全文Feed切换到部分Feed。 他们引用了来自Gawker的Nick Denton的话 ，他说：“ Gawker Media是一家广告支持的公司。 RSS广告从未意识到其潜力。 同时，我们在我们的网站上出售大量广告。 因此，是的，如果有人被摘录引诱，点击就符合我们的利益。” 但是，如果您说的是斯蒂芬(Stephan)，那是真的，如果主流受众还没有弄清楚提要，或者也许他们永远也不会那样阅读内容，那么主流站点提供全文提要的不利之处是什么？ 如果他们的主流受众无论如何都将来到他们的网站并看到他们的广告，那么谁在阅读您的全文供稿？ 您不会蚕食主流受众； 您正在做的只是为听众中的一小部分书呆子提供一些东西。
Stephan: That’s a good point. I would be interested to see what their percentage of readers drop off, if any. I don’t think they’re going to see a huge loss. Maybe that’s the thing, they thought the overhead of hosting RSS feeds, if they host them I don’t know, was too much.
史蒂芬：很好。 我很想知道他们的读者百分比(如果有)下降了。 我认为他们不会蒙受巨大损失。 也许就是这样，他们认为托管RSS feed的开销(如果托管我不知道的话)太多了。
Kevin: Awh.
凯文：噢。
Stephan: Yeah right, exactly.
斯蒂芬：是的，正确。
Kevin: I don’t buy that.
凯文：我不买。
Stephan: I don’t buy that, but I don’t know. I don’t see a negative to giving away the full text if most of your traffic is through the website anyway.
史蒂芬：我不买，但我不知道。 无论如何，如果您的大部分访问量都是通过网站，我不会放弃全文。
Kevin: I think the problem is just that it is counterintuitive. That giving away your content in a form without ads can be beneficial because—and this is something that Felix Salmon writes about in a piece at Reuters. He says, “There’s no evidence at all that truncating your RSS feeds results in higher traffic, and indeed there’s quite a strong case to be made that it works the other way around, and that switching from truncated feeds to full feeds is the thing which results in higher traffic.” And he’s got several case studies that he cites about this. He mentions that The Guardian newspaper—talk about a mainstream publication—moved to full RSS feeds in late 2008, and its web traffic grew dramatically from 25 million to 37 million monthly uniques. Now of course there’s other factors in play there, I mean that just sounds like the growth curve of the Web in general. But it obviously hasn’t hurt them. And I guess the theory behind full text feeds generating more traffic for you is that those people, those nerds who will consume that format of content, are the same people who tend to share your content, promote it through social networking tools like Twitter.
凯文：我认为问题仅仅是违反直觉的。 以没有广告的形式放弃您的内容可能是有益的，因为-这就是Felix Salmon 在路透社的一篇文章中所写的。 他说：“根本没有证据表明截断RSS提要会导致更高的流量，并且确实有充分的理由证明它会反其道而行之，从截断提要切换到完整提要是一件很重要的事情。导致流量增加。” 他为此引用了一些案例研究。 他提到，《卫报》(一种主流出版物)在2008年底转为完整的RSS提要，其网络流量从每月2500万增至每月3700万。 当然，现在还有其他因素在起作用，我的意思是，这听起来一般来说就像Web的增长曲线。 但这显然并没有伤害他们。 而且我猜想，全文供稿背后的理论为您带来了更多的流量，即那些将使用这种格式的内容的人，那些书呆子的人与倾向于共享您的内容并通过Twitter等社交网络工具推广您的内容的人相同。
And so those people in exchange for your content without ads are out there evangelizing your content and generating more traffic for you.
因此，那些在没有广告的情况下交换您内容的人在那里宣传您的内容并为您带来更多流量。
Stephan: Yeah, I agree.
斯蒂芬：是的，我同意。
Kevin: That’s the theory and I’ll be the first to say it’s not an airtight theory but it sounds more sensible then any of the theories for shutting down access to your RSS feeds.
凯文：那是理论，我将是第一个说这不是一个封闭的理论，但是听起来比任何理论都更合理，因为它可以关闭对RSS提要的访问。
Stephan: Yeah, I think just cutting your RSS feeds like that and kind of surprising people out of the blue and then announcing it is the wrong way of doing it. My wife, she reads Deadspin through a feed reader and as soon as she found out, she saw that she was getting half the feed, she was like why would I want to read this anymore? The whole point of me using the feed is so I don’t go to the website and I just read everything quickly, the headlines, and get what I want. And so I told her to vote with her spacebar. Don’t go to it.
斯蒂芬：是的，我认为只是像这样切掉您的RSS提要，并让其他人大吃一惊，然后宣布它是错误的方法。 我的妻子，她通过提要阅读器阅读Deadspin，一经发现，她发现自己得到了一半的提要，就像我为什么还要再阅读一遍？ 我使用提要的全部目的是，所以我不去网站，而只是快速阅读所有内容，头条新闻并获得想要的东西。 所以我告诉她用她的空格键投票。 不要去
Kevin: Yeah, exactly. There’s got to be another site out there just covering the same stuff with full feeds if that’s how you read content, and I sure do, yeah I’m gonna go where I can get the content.
凯文：是的，确实如此。 如果那是您阅读内容的方式，那么那里肯定还有另一个网站会覆盖全部内容并提供完整的供稿。我确实愿意，是的，我要去哪里获取内容。
Stephan: So do you think then that Gruber makes a good point that these companies that are big can benefit from full RSS feeds financially, not just traffic-wise, but financially grow and be as successful as he is with their product or their content?
斯蒂芬：那么您是否认为格鲁伯提出了一个好点，即这些大型公司可以从财务上(不仅在流量方面)受益于完整的RSS提要，而且在财务上可以像他在产品或内容方面一样取得成功并取得成功？
Kevin: I think it’s true. I think that is true. I would put money on that. I don’t think John Gruber proves it with his one man operation, but I think that if a big company like Macworld, like Gawker, approached RSS advertising the way John Gruber approaches his own RSS advertising, which is sourcing ads specifically for RSS, specifically targeted to that audience, presenting them as full posts in the RSS feed, if you did all that I think you would get a return on your investment. And even if you don’t advertise at all in your feeds—and this is not a point that John Gruber makes but I think this is what Felix Salmon is talking about—if you can’t spend the time to generate advertising that is specialized for the RSS medium then put it out there without ads. All signs point to the fact that it’s not going to cost you any traffic. And it seems like Gawker is hedging their bets here. Felix Salmon points out that Gawker still provides what they call a VIP feed; it’s a public URL but it is not advertised on their site anywhere. If you go to Gawker and click the RSS button on your browser you’re going to get their partial feed, but they have a secret URL full feed so that anytime a power user complains they can just go “Yeah subscribe to this URL, don’t worry about it.”
凯文：我认为是真的。 我认为是真的。 我会花钱。 我认为约翰·格鲁伯(John Gruber)不能通过他的单人操作来证明这一点，但是我认为，如果像Macworld这样的大公司，例如高克(Gawker)，以约翰·格鲁伯(John Gruber)处理自己的RSS广告的方式来处理RSS广告，这是专门为RSS采购广告的，如果您做了所有我认为可以从投资中获得回报的内容，则可以专门针对该受众群体，在RSS feed中将其作为完整帖子显示。 即使您根本不在Feed中做广告，这也不是John Gruber讲的重点，但我认为这就是Felix Salmon在说的，如果您不能花费时间来制作专门的广告RSS媒体，然后将其放到那里而没有广告。 所有迹象都表明它不会花费您任何流量。 好像Gawker在这里对冲他们的赌注。 Felix Salmon指出，Gawker仍然提供他们所谓的VIP提要。 这是一个公共网址，但不会在其网站上的任何位置进行广告宣传。 如果您转到Gawker并在浏览器上单击RSS按钮，则将获得其部分供稿，但它们具有秘密的URL完整供稿，因此，只要有权限的用户抱怨他们可以去“就可以订阅此URL，不要不用担心。”
Stephan: That’s an interesting point because I remember Gruber used to have a subscription service where you could pay to get the— I guess it was the full feed back then, I’d have to go back and look. But yeah, and he got rid of it because it just wasn’t worth the implementation that he was doing to get it to work, and he said, I mean he wasn’t seeing the cash flow that he now sees with the full feed, so.
史蒂芬：这是一个有趣的观点，因为我记得格鲁伯曾经有一个订阅服务，您可以付费购买它—我想那是当时的完整提要，我不得不回头看看。 但是，是的，他摆脱了它，因为这样做不值得他执行才能使其生效，他说，我的意思是，他没有看到他现在看到的全部现金流量，所以。
Kevin: Alright. Well, listener, full feed or partial feed, do you care? Is this a factor for you in deciding whether you follow a feed or not? And on your own site have you had to wrestle with this decision? Let us know in the comments for this episode, head to sitepoint.com/podcast and let us know, we’ll be sure to read out your comments next news show.
凯文：好吧。 好吧，听众，全部订阅或部分订阅，您在乎吗？ 这是您决定是否遵循Feed的因素吗？ 在您自己的网站上，您是否不得不为这个决定而苦恼？ 在此集的评论中让我们知道，请转到sitepoint.com/podcast ，让我们知道，我们一定会在下一个新闻节目中朗读您的评论。
Let’s take a look at a couple of quick stories. Stephan, you flagged a link about Flash and Virgin America, what’s that all about?
让我们看几个简单的故事。 史蒂芬(Stephan)，您标记了有关Flash和Virgin America的链接 ，这是怎么回事？
Stephan: Virgin America is kind of a trendy carrier here by Richard Branson in the United States, it’s his low cost carrier that he has. And they’re kind of – I call them kind of like the trendy airline. And they actually have decided, their CTO has announced that they’re killing off Flash, and they actually have on their homepage. And to be clear, they’ve only killed it on the homepage, there’s still places in the site where there’s Flash elements. But his reasoning is that they don’t want to alienate iPhone users and users that do not have Flash installed on their devices. And so they’re hoping to move to a more open and usable website and this was one of those ways of doing that. So I thought it was interesting that they cut it out completely off the homepage.
史蒂芬：维珍美国航空是理查德·布兰森(Richard Branson)在美国的一种时髦航空母舰，这是他拥有的低成本航空母舰。 他们有点–我称之为时髦航空公司。 他们实际上已经决定，他们的CTO宣布他们正在杀死Flash，实际上他们已经出现在其主页上。 需要明确的是，他们只是在首页上将其杀死，该站点中仍然存在Flash元素。 但他的理由是，他们不想疏远iPhone用户和未在其设备上安装Flash的用户。 因此，他们希望转到一个更加开放和可用的网站，而这就是做到这一点的方式之一。 因此，我认为很有趣的是他们将其完全从首页上删除了。
Kevin: We’ve talked about this at some length before, but I think the one thing we can probably all agree on is that days of Flash for Flash’s sake are very numbered.
凯文：我们之前已经讨论过很长时间了，但是我认为我们可能都可以同意的一件事是，为了Flash的缘故，Flash的日子非常多。
Stephan: Yeah.
斯蒂芬：是的。
Kevin: Like you can make an argument that you want to use Flash for a particular thing because it provides a superior experience, but the days of landing on the homepage of a site and its just a Flash movie just because that’s what the developer’s used to or they can create exactly what they had in Photoshop just by dragging and dropping the resources into Flash, those days are numbered. That’s just not an acceptable experience for an iPhone user to land at your homepage and see a big blue plug-in missing box.
凯文(Kevin)：就像您可以说要在特定事物上使用Flash一样，因为它可以提供出色的体验，但是，登陆网站首页和播放Flash电影的日子仅仅是因为开发人员习惯于使用Flash或只需将资源拖放到Flash中，就可以创建与Photoshop完全一样的东西，这些日子已经编号了。 对于iPhone用户来说，进入您的主页并看到一个蓝色的大缺失插件框是不可接受的体验。
Stephan: Especially when they’re trying to cater to a younger audience that flies their airline that’s using the iPhone a lot.
斯蒂芬：尤其是当他们试图迎合那些经常乘坐使用iPhone的航空公司的年轻观众时。
Kevin: Oh yeah. Seriously.
凯文：是的。 说真的
Stephan: You want to be able to go on there, book your— They’re moving to paperless tickets, so they want to make it as seamless as possible, and this seems like a good first step, so it’s interesting to see.
史蒂芬(Stephan)：您希望能够继续在那里预订，他们正准备购买无纸机票，因此他们希望尽可能地保持无缝，这似乎是一个很好的第一步，因此很有趣。
Kevin: Brad, who’s not with us today, but he did submit a link and this is from an interview with Google’s Matt Cutts seemingly confirming that 301 redirects result in page rank loss. And I think we’ll get it out of the way, we’ll say the disclaimer here that neither Stephan or I consider ourselves search marketing gurus, right Stephan?
凯文：布拉德(Brad)，今天不在我们身边，但是他确实提交了链接，这是来自对Google的马特·卡茨(Matt Cutts)的一次采访，看似证实301重定向会导致网页排名下降。 我想我们会摆脱它，在这里说免责声明，Stephan或我都不认为自己是搜索营销专家，Stephan吗？
Stephan: Oh absolutely, yeah, we’re not.
斯蒂芬：哦，绝对，是的，我们不是。
Kevin: You don’t have a secret life as a search marketing guru?
凯文：您没有搜索营销专家的秘密生活吗？
Stephan: No. Sometimes I wish I did though just so I could tell people that.
斯蒂芬：不。有时候我希望我能做到，但是我可以告诉别人。
Kevin: I think it’s not the— It doesn’t have the stigma it used to have. Like for a while there everyone was a search marketing guru, and then it was like “aw, come on”; today I think that’s the social media guru. I bet there’s a lot of people wandering around South by Southwest handing out business cards that say ‘social media expert’ on it.
凯文：我认为不是—它没有以前的污名。 好像有一段时间，每个人都是搜索营销专家，然后就像“ aw，加油”。 今天，我认为那是社交媒体专家。 我敢打赌，西南地区有很多人在西南徘徊，发放名片上写着“社交媒体专家”的名片。
Stephan: That’s a good question for Patrick when he gets back, how many people on his cards, how many people that’s their title. I’d be interested.
斯蒂芬：这对帕特里克回来时是个好问题，他的牌上有多少人，有多少人是他们的头衔。 我会感兴趣的。
Kevin: I hope that’s not Patrick’s title.
凯文：我希望那不是帕特里克的头衔。
Stephan: I don’t think it is.
史蒂芬：我认为不是。
Kevin: Okay, good. But yeah, for a while there it seemed like everyone was a search engine optimization expert. But I think the pretenders have sort of gotten distracted by social media, and the people who are still exploring search marketing seem to take it pretty seriously. So this is an interview, wow, one of these oddball consulting sites, it’s not a— I like these stories that come from sites that you’ve never heard from before because I get a lot of link love, it’s usually because I have something really important to say. But this guy caught up, this guy Eric Enge caught up with Matt Cutts and really this is a deep interview where, I don’t know, you know when you sit down with someone from Google or Microsoft and you sort of wonder how far you can push it? Like you want to ask the Microsoft guy so what’s the release date of Internet Explorer 9?
凯文：好的，很好。 但是，是的，有一段时间似乎每个人都是搜索引擎优化专家。 但是我认为这些伪装者已经被社交媒体分散了注意力，并且仍在探索搜索营销的人们似乎非常重视它。 所以，这是一次采访，哇，这些怪诞的咨询网站之一，不是-我喜欢这些故事，这些故事来自您从未听说过的站点，因为我得到了很多链接爱，通常是因为我有一些东西真的很重要。 但是这个人赶上来了，这个人Eric Enge赶上了Matt Cutts，这真的是一次深度采访，我不知道，当您与Google或Microsoft的某个人坐下来时，您会想知道您走了多远可以推吗？ 就像您想问微软的那家伙，那么Internet Explorer 9的发布日期是什么？
Stephan: (chuckle)
斯蒂芬：(笑)
Kevin: But you’re afraid he’s going to go, “Yeah, this interview is over!” But this guy asks Matt Cutts if Google, all of the questions that I would love to ask a Google search guy, afraid that he would end the interview, but he actually provides really good answers.
凯文：但是你担心他会走，“是的，这次采访结束了！” 但是这个人问马特·卡茨(Matt Cutts)，如果我不想问谷歌搜索人员，所有的问题我都想问谷歌，他害怕结束采访，但他确实提供了很好的答案。
This one question, Eric Enge says, “Let’s say you move from one domain to another and you write yourself a nice little statement that basically instructs the search engine and any user agent on how to remap from one domain to the other. In a scenario like this is there some loss in page rank”—and he says earlier on when he says page rank he means the general link juice because page rank is a very small factor in Google nowadays, but just the general link juice that Google passes on from those pages—“is there some loss in page rank that can take place simply because the user who originally implemented a link to the site didn’t link to it on the new domain?” Matt Cutts replies, “I can certainly see how there could be some loss of page rank. I’m not a hundred percent sure whether the crawling and indexing team has implemented that sort of natural page rank decay, so I will have to go and check on that specific case.” And then there’s a note saying that Matt Cutts got back to him via email and says, “Matt confirmed that this is in fact the case, there is some loss of page rank through a 301 redirect.”
埃里克·恩格(Eric Enge)说，这是一个问题，“假设您从一个域转移到另一个域，然后给自己写了一条漂亮的小语句，它基本上指导搜索引擎和任何用户代理如何从一个域重新映射到另一个域。 在这样的情况下，页面排名会有所损失”，他在前面说页面排名时表示，他的意思是一般链接，因为页面排名在当今的Google中是很小的因素，而仅仅是Google的一般链接。从这些页面传来-“仅仅是因为最初实现了到站点的链接的用户未在新域上链接到该站点，页面排名是否会因此而损失？” 马特·卡茨(Matt Cutts)回答说：“我当然可以看到页面排名可能会有所下降。 我不确定百分之一百的爬网和索引团队是否已经实现了这种自然的页面排名衰减，所以我将不得不去检查这种特定情况。” 然后有一条纸条说，马特·卡茨(Matt Cutts)通过电子邮件回信给他，并说：“马特(Matt)确认确实是这种情况，通过301重定向，页面排名有所损失。”
This interview is full of nuggets like this. It’s like every paragraph has got another little interesting little tidbit about Google’s search ranking algorithms. It’s more concentrated actual facts from the horse’s mouth about Google’s search marketing tips then I have ever seen in one place before. So if you only read one search engine optimization article this year I recommend this interview, it’s really good.
这次采访充满了像这样的掘金。 就像每个段落都对Google的搜索排名算法产生了另一个有趣的小窍门。 从马口说起的关于Google搜索营销技巧的实际事实比我以前在一个地方见过的要多。 因此，如果您今年只阅读一篇搜索引擎优化文章，我建议您接受本次采访，那真的很好。
Stephan: Interesting.
斯蒂芬：有趣。
Kevin: The big story today though is the Internet Explorer 9 platform preview from Microsoft. Which neither Stephan nor I have installed, is that right Stephan?
凯文：今天最重要的是Microsoft的Internet Explorer 9平台预览版 。 斯蒂芬和我都没有安装，斯蒂芬对吗？
Stephan: Yeah, I haven’t installed it—on my Mac.
史蒂芬：是的，我还没有安装它-在我的Mac上。
Kevin: You need Windows, and unlike the other versions of Internet Explorer where you can download a virtual machine so you can run it in a VM on your Windows box, there is not a VM for the IE 9 developer preview yet. And the reason for that is this, for the first time, is an official version of the Internet Explorer engine, and this is the rendering engine the JavaScript engine, all that stuff bundled together in a stand alone application that you can install and run side by side with Internet Explorer 8, Internet Explorer 7, whatever you happen to have installed on your machine. So it is a true standalone version of the Internet Explorer 9 in development rendering engine. And I think if nothing else that deserves serious congratulations because they’ve been saying for years they can’t do that, it’s hard to do, it doesn’t provide a true representation of the Internet Explorer developer experience. But they’ve done it. They’ve finally done exactly what we’ve been asking for. And I hope they continue doing this beyond the development process for the browser, personally. But this is a preview of where they’re up to in developing Internet Explorer 9, and it is really exciting.
凯文：您需要Windows，并且与其他版本的Internet Explorer不同，在Internet Explorer上您可以下载虚拟机，以便可以在Windows框中的VM中运行它，但还没有用于IE 9开发人员预览的VM。 这样做的原因是，这是Internet Explorer引擎的正式版本，这是JavaScript引擎的呈现引擎，所有这些东西捆绑在一个独立的应用程序中，您可以在侧面安装和运行与Internet Explorer 8，Internet Explorer 7并排运行，无论您碰巧安装在计算机上的是什么。 因此，它是开发呈现引擎中Internet Explorer 9的真正独立版本。 而且我认为，如果因为他们多年来一直在说自己不能做到而值得称赞的其他事情，那是很难做到的，它不能真正代表Internet Explorer开发人员的经验。 但是他们做到了。 他们终于完全按照我们的要求做了。 我希望他们继续亲自完成浏览器开发过程之外的工作。 但这是他们开发Internet Explorer 9的前瞻性预览，这确实令人兴奋。
Stephan: Yeah, it’s fast.
斯蒂芬：是的，很快。
Kevin: Well, yeah! I was going to start talking about all the standards features, but let’s talk about speed. The scripting engine, which they say— Their new script engine, they’re calling it Chakra, and their trick, the thing that they do that no other browser does with JavaScript, is that it compiles JavaScript in the background on a separate CPU core. Which sounds crazy to put something on a separate CPU core it just means a separate execution thread in the app. Really it means that in the background separate from all the other stuff the browser is doing it can allocate one of the multiple CPU cores that you typically have in machines these days to compiling the JavaScript in a fast executing thing. And it’s really paid off. Just in this developer preview looking at the Sun Spider benchmark, which I think is developed by the WebKit people, so I guess you’d expect Safari to do especially well on this because it’s by the same developers as the Safari rendering engine. Internet Explorer 9 developer preview beats Firefox 3.6 and 3.7 (3.7 not even released yet, 3.7 alpha). It also, well it completely beats Internet Explorer 8 which is the slowest browser on the graph they show here. Opera 10.1 the second slowest gets its pants beat. But things that are still faster than Internet Explorer 9 include Safari, Chrome, and Opera 10.5 just released for Windows and still in beta for other platforms. Opera 10.5 is still the fastest JavaScript executing browser on this graph. But Internet Explorer 9 right in the middle of the pack, but the difference between it and the faster browsers is extremely slim. It’s right up there in the same league as the fastest JavaScript executing browsers out there, which is really amazing, I never thought we’d see the day where Internet Explorer was playing in the same league as the other browsers.
凯文：恩，是的！ 我将开始谈论所有标准功能，但让我们谈谈速度。 他们说 ，脚本引擎是他们的新脚本引擎，他们称其为Chakra，而他们的窍门是其他浏览器无法使用JavaScript来完成的，那就是它在单独的CPU内核中后台编译JavaScript。 。 将某些东西放在单独的CPU内核上听起来很疯狂，但这仅意味着应用程序中有单独的执行线程。 确实，这意味着浏览器可以在后台将所有其他内容分离开来，以分配这些天您通常在计算机中拥有的多个CPU内核之一，从而以快速执行的方式编译JavaScript。 而且真的很值得。 只是在此开发人员预览中查看了Sun Spider基准测试 (我认为它是由WebKit开发的)，因此我想您会期望Safari在此方面做得特别好，因为它与Safari渲染引擎由同一开发人员共同开发。 Internet Explorer 9开发人员预览版优于Firefox 3.6和3.7(3.7尚未发布，3.7 alpha)。 它还完全击败了Internet Explorer 8，后者是他们在此处显示的图表中最慢的浏览器。 第二慢的Opera 10.1击败了裤子。 但是仍然比Internet Explorer 9快的东西包括Safari，Chrome和Opera 10.5，它们刚刚在Windows上发布，而在其他平台上仍处于测试阶段。 Opera 10.5仍然是此图中执行速度最快JavaScript浏览器。 但是Internet Explorer 9恰好位于包装的中间，但是它与速度更快的浏览器之间的区别非常小。 它与最快的执行JavaScript的浏览器处于同一联盟中，这真是太神奇了，我从没想到我们会看到Internet Explorer与其他浏览器处于同一联盟的一天。
But what really impresses me, like I said, is the features. It would be one thing for them to say, screw it, we’re just going to focus on performance in this release, but here’s the quote, “In IE 9 we’re doing for the rest of the platform what we did for CSS 2.1 in Internet Explorer 8.” Say what you will about Internet Explorer 8, Microsoft came to the party in CSS 2.1 and implemented every feature of CSS 2.1. It had the most CSS 2.1 implementation of all browsers. Since CSS 3 is still largely a draft specification you couldn’t really fault them for saying “Look, we know support the latest finalized CSS standard in our browser.” And now it looks like in Internet Explorer 9 their aiming much bigger. They say they’re going to support HTML5, they’re going to support a whole bunch of document object model, DOM standards, that they haven’t supported before. CSS 3 they’re supporting big chunks of, and SVG, scalable vector graphics, they’ve added support for that. This is huge. If they had announced support for any one of those things I would’ve been excited about the Internet Explorer 9 release, but it seems like they’re trying to do it all.
但是，真正使我印象深刻的是这些功能。 让他们说一句话，把它搞砸，我们将只专注于此版本中的性能，但是这句话是这样的：“在IE 9中，我们正在为平台的其余部分做我们为CSS做的工作在Internet Explorer 8中为2.1。” 说出您对Internet Explorer 8的看法，Microsoft参加CSS 2.1并实现了CSS 2.1的所有功能。 它具有所有浏览器中最多CSS 2.1实现。 由于CSS 3仍是一个主要的规范草案，您不能对他们说“看起来，我们知道在我们的浏览器中支持最新的最终CSS标准”感到不满。 现在看来，在Internet Explorer 9中，他们的目标更大了。 他们说他们将支持HTML5，他们将支持以前不曾支持的一整套文档对象模型，DOM标准。 他们支持CSS 3和SVG的大块可扩展矢量图形，他们增加了对此的支持。 这是巨大的。 如果他们宣布支持其中任何一种功能，那么Internet Explorer 9发行版将让我很兴奋，但似乎他们正在尝试全部完成。
Stephan: They’re kind of jumping all in. It’s cool, I’m glad. How can we be negative about this at all? I think this is great.
史蒂芬：他们有点全力以赴。很酷，我很高兴。 我们怎么能对此持否定态度呢？ 我认为这很棒。
Kevin: And managing to boost speed. For the geeks in the audience, what do these– Like you can say HTML5, DOM, CSS 3; what are the actual features? Well, we have now finally border-radius, rounded corners in Internet Explorer 9. This is the last major browser to add this, so the days of creating images for your rounded corners if you want them in all browsers are numbered. I’d say as soon as Internet Explorer 9 is released there is no longer any real reason to fake those rounded corners when you can just do them in your CSS and tell Internet Explorer 8 users “You want the pretty, do the upgrade, really”. DOM events, at long last, for the JavaScript geeks in the audience you know what I’m talking about. As big a stride as Microsoft has made in JavaScript performance over the years, writing JavaScript for Internet Explorer has still been a huge pain if only because you have to handle events completely differently. If you want to say do something on click you had to do it one way for all the other browsers, the standards way for all the other browsers, and then the Internet Explorer only way. It seemed like this was the last major piece of, you know, back in the late 90’s you always had to do if it’s Netscape 4 do this, if Internet Explorer do that?
凯文：并且设法提高速度。 对于听众来说，这些是做什么的-就像您可以说HTML5，DOM，CSS 3； 实际功能是什么？ 好了，我们现在终于在Internet Explorer 9中获得了边框半径和圆角。这是最后一个添加此功能的主要浏览器，因此，如果要在所有浏览器中为圆角创建图像，则要进行编号。 我要说的是，Internet Explorer 9发行后，只要在CSS中进行修饰并告诉Internet Explorer 8用户，便不再有任何真正的理由去伪造这些圆角，“ ”。 最终，对于受众中JavaScript怪才来说，DOM事件就知道我在说什么。 多年来，Microsoft在JavaScript性能方面取得了长足进步，但仅由于您必须完全不同地处理事件而为Internet Explorer编写JavaScript仍然是一个巨大的痛苦。 如果要说单击即可执行操作，则必须对所有其他浏览器采用一种方法，对所有其他浏览器采用标准方法，然后仅对Internet Explorer执行。 好像这是90年代末期的最后一个主要部分，如果是Netscape 4，则必须执行此操作，如果Internet Explorer可以，则必须执行此操作？
Stephan: Mmm-mm.
斯蒂芬：嗯。
Kevin: This was the last major piece of code where you still had to do that today. DOM events, finally, like this is gonna— When Internet Explorer 9 becomes pervasive this is going to lift huge chunks of code out of libraries like jQuery and things like that that have to bridge that gap. And then things like CSS 3 selectors, advanced selectors, so you can write CSS rules that style every second table row, that kind of stuff, they’re really putting the final pieces in place there. HTML5 video is not in this preview, but it is coming in the Internet Explorer 9 browser they say. They say it’s coming in a future preview with H.264 video; so the same video standard that Safari 4 supports. This is amazing! Internet Explorer 9’s gonna do it all.
凯文：这是最后的主要代码段，今天您仍然必须这样做。 最终，将发生DOM事件，当Internet Explorer 9普及时，它将从jQuery之类的库中抽取大量代码，而诸如此类的事情必须弥合这一差距。 And then things like CSS 3 selectors, advanced selectors, so you can write CSS rules that style every second table row, that kind of stuff, they're really putting the final pieces in place there. HTML5 video is not in this preview, but it is coming in the Internet Explorer 9 browser they say. They say it's coming in a future preview with H.264 video; so the same video standard that Safari 4 supports. 这真太了不起了！ Internet Explorer 9's gonna do it all.
Stephan: I’m glad. It’s great. I think it’s good news. Less work for people, developers in the future, it’s good.
Stephan: I'm glad. 这很棒。 I think it's good news. Less work for people, developers in the future, it's good.
Kevin: Yeah. SVG is great, the version that’s in the developer preview is still very early, there’s a lot of missing features still, but they say they’re aiming for similar feature richness as you get in Firefox. So this is another blow to Flash. I hate to bang on Flash in this podcast over and over again, but you can say that HTML5 canvas, and stuff like that, was a replacement for Flash, but doing stuff in Canvas can be a real pain, whereas in Flash you can say look I want to draw this logo and then have it drift across. Where in Canvas you had to repaint that logo for every frame, in Flash you could just say move that object from there to there. SVG is the open standard for doing that same sort of thing: create shapes, create drawing elements, and then manipulate them with JavaScript without having to redraw them and keep track of their state in your code. So yeah, sorry for the non-geeks in the audience, I just have to geek out at this stuff.
凯文：是的。 SVG is great, the version that's in the developer preview is still very early, there's a lot of missing features still, but they say they're aiming for similar feature richness as you get in Firefox. So this is another blow to Flash. I hate to bang on Flash in this podcast over and over again, but you can say that HTML5 canvas, and stuff like that, was a replacement for Flash, but doing stuff in Canvas can be a real pain, whereas in Flash you can say look I want to draw this logo and then have it drift across. Where in Canvas you had to repaint that logo for every frame, in Flash you could just say move that object from there to there. SVG is the open standard for doing that same sort of thing: create shapes, create drawing elements, and then manipulate them with JavaScript without having to redraw them and keep track of their state in your code. So yeah, sorry for the non-geeks in the audience, I just have to geek out at this stuff.
The last thing that really surprised me in their list of features is XHTML support. Talk about coming late to the party. Everyone has given up on XHTML. The W3C has stopped development of XHTML technically. I suppose you can still deliver HTML5 as an XML document, and that is what we will now call XHTML going forward. But I don’t— oh!
The last thing that really surprised me in their list of features is XHTML support. Talk about coming late to the party. Everyone has given up on XHTML. The W3C has stopped development of XHTML technically. I suppose you can still deliver HTML5 as an XML document, and that is what we will now call XHTML going forward. But I don't— oh!
Stephan: So they’re still late to the party that the party’s actually been broken up by the cops and everybody’s gone home.
Stephan: So they're still late to the party that the party's actually been broken up by the cops and everybody's gone home.
Kevin: Yeah, exactly! And they’re like “Hey I’m here with the booze! Where’d everyone go?” I can’t understand this; it’s like congratulations for finally doing it. I don’t know why they’re doing it.
Kevin: Yeah, exactly! And they're like “Hey I'm here with the booze! Where'd everyone go?” I can't understand this; it's like congratulations for finally doing it. I don't know why they're doing it.
Yeah. For the first half of the past decade everyone was saying if only Internet Explorer would support XHTML we could do this, we could do that. It would enable semantic web, it would enable greater validation of websites and creation of custom tag sets that you could integrate with HTML. And then everyone kind of went well I guess they’re never gonna do it, we’re gonna have to find other ways to do all those things. And that generated efforts like microformats, and even HTML5 to some extent. Saying oh I guess we’re gonna have to go back to the drawing board and actually add some new tags to HTML—from many perspectives that’s what’s most exciting about HTML5. That would never have happened if Microsoft had gotten on board of the HTML train back when everyone was saying that’s the way to add new features to HTML. And now when everyone has moved on and found other ways to do these things, here comes XHTML support in Internet Explorer. I don’t get it but I love it anyway.
是的 For the first half of the past decade everyone was saying if only Internet Explorer would support XHTML we could do this, we could do that. It would enable semantic web, it would enable greater validation of websites and creation of custom tag sets that you could integrate with HTML. And then everyone kind of went well I guess they're never gonna do it, we're gonna have to find other ways to do all those things. And that generated efforts like microformats, and even HTML5 to some extent. Saying oh I guess we're gonna have to go back to the drawing board and actually add some new tags to HTML—from many perspectives that's what's most exciting about HTML5. That would never have happened if Microsoft had gotten on board of the HTML train back when everyone was saying that's the way to add new features to HTML. And now when everyone has moved on and found other ways to do these things, here comes XHTML support in Internet Explorer. I don't get it but I love it anyway.
Reading their announcements I wonder how Microsoft is thinking about HTML5, and there was a Tweet earlier this week that I thought was particularly apt, and this is from John Allsopp who runs the Web Directions conferences. He said on Twitter, “HTML5 is the new Ajax. Discuss.” And I just want to read you a couple paragraphs from Microsoft’s Dean—I always get his name mixed up—Dean Hachmovitch, who is the general manager of Internet Explorer. This is from the Internet Explorer 9 developer preview announcement. “HTML5 applications will need great script performance and consistent same markup, same results across browsers. Great HTML5 applications will build on that foundation and go further, providing game-like interactivity and movie-like graphical richness to the user experience. Today’s standards markup web pages and today’s browsers are limited in this regard because they can only use a fraction of what PC hardware and the operating system can do. HTML5 applications will demand more.” Do you get the sense that when he says HTML5 he’s not referring to the HTML5 standards, the tags, the parsing rules? It seems like HTML5 is this buzz word that’s taken on— It’s web 2.0, it’s Ajax, it’s the next big wave of innovation on the web.
Reading their announcements I wonder how Microsoft is thinking about HTML5, and there was a Tweet earlier this week that I thought was particularly apt, and this is from John Allsopp who runs the Web Directions conferences. He said on Twitter, “HTML5 is the new Ajax. Discuss.” And I just want to read you a couple paragraphs from Microsoft's Dean—I always get his name mixed up—Dean Hachmovitch, who is the general manager of Internet Explorer. This is from the Internet Explorer 9 developer preview announcement . “HTML5 applications will need great script performance and consistent same markup, same results across browsers. Great HTML5 applications will build on that foundation and go further, providing game-like interactivity and movie-like graphical richness to the user experience. Today's standards markup web pages and today's browsers are limited in this regard because they can only use a fraction of what PC hardware and the operating system can do. HTML5 applications will demand more.” Do you get the sense that when he says HTML5 he's not referring to the HTML5 standards, the tags, the parsing rules? It seems like HTML5 is this buzz word that's taken on— It's web 2.0, it's Ajax, it's the next big wave of innovation on the web.
Stephan: That’s what he’s implying…
Stephan: That's what he's implying…
Kevin: Yeah!
凯文：是的！
Stephan: It’s just a word.
Stephan: It's just a word.
Kevin: To some extent I think you could take the actual features of HTML5, remove them from what’s coming in the Web, and all the other stuff, the CSS 3, the JavaScript performance, SVG, all that stuff put together would still let you do everything he’s talking about when he says HTML5.
Kevin: To some extent I think you could take the actual features of HTML5, remove them from what's coming in the Web, and all the other stuff, the CSS 3, the JavaScript performance, SVG, all that stuff put together would still let you do everything he's talking about when he says HTML5.
Stephan: Mmm-mm.
Stephan: Mmm-mm.
Kevin: So I don’t really think it’s about HTML5. I think it’s unfortunate for the HTML5 standard that everyone is— Well, is it unfortunate or is it a boon for the standard?
Kevin: So I don't really think it's about HTML5. I think it's unfortunate for the HTML5 standard that everyone is— Well, is it unfortunate or is it a boon for the standard?
Stephan: Well, I mean let’s think about Ajax. Ajax then just became a thing that everyone just knows how to do. They just didn’t call it Ajax anymore, right?
Stephan: Well, I mean let's think about Ajax. Ajax then just became a thing that everyone just knows how to do. They just didn't call it Ajax anymore, right?
Kevin: Right.
凯文：对。
Stephan: To me, that’s a good thing.
Stephan: To me, that's a good thing.
Kevin: Well, it got to the point where as soon as you saw a JavaScript-powered widget on the page that you could drag or, you know, if you had a slider control on the page that you could click and drag with your mouse to select a number, that became Ajax, people would say “Oh I love that piece of Ajax on the page”. And there was no Ajax going on there, it was just JavaScript moving a thing in response to the mouse. We are already at the point where people are saying “well this is an HTML5 application”, and in fact there is no HTML5 specific features in the page that they’re talking about. But is that good for the HTML5 spec? Does it mean that all these features that only developers and nerds like me care about are going to get implemented just because people are excited about anything called HTML5?
Kevin: Well, it got to the point where as soon as you saw a JavaScript-powered widget on the page that you could drag or, you know, if you had a slider control on the page that you could click and drag with your mouse to select a number, that became Ajax, people would say “Oh I love that piece of Ajax on the page”. And there was no Ajax going on there, it was just JavaScript moving a thing in response to the mouse. We are already at the point where people are saying “well this is an HTML5 application”, and in fact there is no HTML5 specific features in the page that they're talking about. But is that good for the HTML5 spec? Does it mean that all these features that only developers and nerds like me care about are going to get implemented just because people are excited about anything called HTML5?
Stephan: I don’t think so.
Stephan: I don't think so.
Kevin: No?
凯文：不？
Stephan: No. I just— I don’t see it. I mean people are just going around looking at websites going “Oh that’s HTML5”, well then that’s just as ignorant as saying a JavaScript widget is Ajax. I mean it’s—
Stephan: No. I just— I don't see it. I mean people are just going around looking at websites going “Oh that's HTML5”, well then that's just as ignorant as saying a JavaScript widget is Ajax. I mean it's—
Kevin: But maybe ignorance is good in this case.
Kevin: But maybe ignorance is good in this case.
Stephan: I guess so. I guess it could be, yeah.
Stephan: I guess so. I guess it could be, yeah.
Kevin: I want the <article> tag, I want the heading group tag. These are features of HTML5 that seriously no one cares about except the markup nerds, but they are going to get implemented in browsers because people are going “woo hoo, we want to say that our browser supports HTML5.”
Kevin: I want the <article> tag, I want the heading group tag. These are features of HTML5 that seriously no one cares about except the markup nerds, but they are going to get implemented in browsers because people are going “woo hoo, we want to say that our browser supports HTML5.”
Stephan: Yep.
斯蒂芬：是的 。
Kevin: Yeah. Well, hmm, I don’t know. Which is better, people actually knowing what they’re talking about or me getting the features that only I care about?
凯文：是的。 Well, hmm, I don't know. Which is better, people actually knowing what they're talking about or me getting the features that only I care about?
The last thing that Microsoft announces with this developer preview is that they’re revamping the way they’re accepting feedback on their browser previews. First of all they say they’re gonna try and aim for a new developer preview release roughly every eight weeks, right up to the release of Internet Explorer 9. And they still haven’t given any kind of picture of when that’s going to be. I’d be surprised if it’s in 2010 at this point. They’ve got so much work ahead them, things like the SVG support, that it’s still very much a work in progress in this preview. I’d say early 2011, if I were a betting man that’s where I would put my money. So there’s quite a few developer preview releases between now and then if they’re doing one every two months. And they say that—this was a big criticism for the Internet Explorer 8 process—they were only accepting bug reports from registered Microsoft sort of partner developers. If you were in a Microsoft developer program you could submit a bug, otherwise you were out of luck. And understandably people were pretty upset about that. So they say they are committing to opening up that bug reporting process, and in fact the developer preview now has a menu item that lets anyone report a bug. And anyone will be able to view that bug database, and this is— and they are also saying they are going to read every single bug report that they receive. I suppose for me that goes without saying.
The last thing that Microsoft announces with this developer preview is that they're revamping the way they're accepting feedback on their browser previews. First of all they say they're gonna try and aim for a new developer preview release roughly every eight weeks, right up to the release of Internet Explorer 9. And they still haven't given any kind of picture of when that's going to be. I'd be surprised if it's in 2010 at this point. They've got so much work ahead them, things like the SVG support, that it's still very much a work in progress in this preview. I'd say early 2011, if I were a betting man that's where I would put my money. So there's quite a few developer preview releases between now and then if they're doing one every two months. And they say that—this was a big criticism for the Internet Explorer 8 process—they were only accepting bug reports from registered Microsoft sort of partner developers. If you were in a Microsoft developer program you could submit a bug, otherwise you were out of luck. And understandably people were pretty upset about that. So they say they are committing to opening up that bug reporting process, and in fact the developer preview now has a menu item that lets anyone report a bug. And anyone will be able to view that bug database, and this is— and they are also saying they are going to read every single bug report that they receive. I suppose for me that goes without saying.
Stephan: That infers a little bit that maybe they weren’t before.
Stephan: That infers a little bit that maybe they weren't before.
Kevin: Yeah, exactly. The big challenge they say is that they get a lot of bug reports that say things like, “Make Internet Explorer more standards compliant.” And yeah, is that a useful bug report? I don’t think so.
凯文：是的，确实如此。 The big challenge they say is that they get a lot of bug reports that say things like, “Make Internet Explorer more standards compliant.” And yeah, is that a useful bug report? 我不这么认为。
Stephan: To the person that submitted it maybe.
Stephan: To the person that submitted it maybe.
Kevin: “Switch to the WebKit rendering engine!” I’m sure there’s some people in our audience who believe that should be done, and maybe the Web would be a better place if they did, but Microsoft’s never gonna do that, and that’s not a constructive piece of criticism when it comes to feedback, a bug report on a Beta. So that’s their challenge is that they have to deal with all of that cruft, but congratulations for stepping up and actually saying you’re gonna do that.
Kevin: “Switch to the WebKit rendering engine!” I'm sure there's some people in our audience who believe that should be done, and maybe the Web would be a better place if they did, but Microsoft's never gonna do that, and that's not a constructive piece of criticism when it comes to feedback, a bug report on a Beta. So that's their challenge is that they have to deal with all of that cruft, but congratulations for stepping up and actually saying you're gonna do that.
But like I said at the start, neither Stephan or I have installed this developer preview. I will get around to doing so in my Windows development virtual machine at some point this week, but listeners, if you have installed the IE 9 developer preview and pointed it at your website; I want to know what you saw. Did your site break? Did features of your site that only work in more standards compliant browsers suddenly come to life? Did you see rounded corners where there weren’t any rounded corners before in Internet Explorer? I would love to hear that kind of story. Or if your site just blew apart and fell in a heap I’d like to hear that too. We’d love to get a picture of just how far along this browser engine is. Is it something that you would actually like to see in a browser? Would you like to see Microsoft releasing these kind of updates to their finished browser for end users to use? Would that be a good thing or is it still too much of a work in progress, a crashy mess that it really should just be for developers? That’s what we want to hear. Head over to sitepoint.com/podcast and leave a comment to let us know.
But like I said at the start, neither Stephan or I have installed this developer preview. I will get around to doing so in my Windows development virtual machine at some point this week, but listeners, if you have installed the IE 9 developer preview and pointed it at your website; I want to know what you saw. Did your site break? Did features of your site that only work in more standards compliant browsers suddenly come to life? Did you see rounded corners where there weren't any rounded corners before in Internet Explorer? I would love to hear that kind of story. Or if your site just blew apart and fell in a heap I'd like to hear that too. We'd love to get a picture of just how far along this browser engine is. Is it something that you would actually like to see in a browser? Would you like to see Microsoft releasing these kind of updates to their finished browser for end users to use? Would that be a good thing or is it still too much of a work in progress, a crashy mess that it really should just be for developers? That's what we want to hear. Head over to sitepoint.com/podcast and leave a comment to let us know.
Before we get to our host spotlights I wanted to touch on a bit of listener feedback that we got on podcast 51, which was when we talked about designer who can’t code. Were you here for that, Stephan?
Before we get to our host spotlights I wanted to touch on a bit of listener feedback that we got on podcast 51, which was when we talked about designer who can't code. Were you here for that, Stephan?
Stephan: Yeah. Yeah, I was here.
斯蒂芬：是的。 Yeah, I was here.
Kevin: Yeah. So how would you summarize where we landed on that? Should web designers be able to code for them to call themselves web designers?
凯文：是的。 So how would you summarize where we landed on that? Should web designers be able to code for them to call themselves web designers?
Stephan: I think it was just kind of split down the middle. I mean I’m kind of torn on the subject, like I said before. I see the point of why we would want web designers to be able to code, but I also see the beauty of the art side of it, so. I don’t know, maybe I can make some enemies on Twitter, you know.
Stephan: I think it was just kind of split down the middle. I mean I'm kind of torn on the subject, like I said before. I see the point of why we would want web designers to be able to code, but I also see the beauty of the art side of it, so. I don't know, maybe I can make some enemies on Twitter, you know.
Kevin: Well, I have to thank our listeners because they wrote in with a whole bunch of really thoughtful comments. Some of them are like blog post lengths of their own. So I encourage you to head over to sitePpint.com/podcast and check out the comments on podcast 51 if you’re interested in this issue.
Kevin: Well, I have to thank our listeners because they wrote in with a whole bunch of really thoughtful comments. Some of them are like blog post lengths of their own. So I encourage you to head over to sitePpint.com/podcast and check out the comments on podcast 51 if you're interested in this issue.
There’s some really interesting takes on it but a couple that I wanted to read out, Luciano Fuentes says, “I’m not really sure why the “designers should know how to code” tweet caused such a stir. It’s like saying “interior designers should know how to tile a bathroom”. It’s not necessary but it sure helps to understand your medium.”
There's some really interesting takes on it but a couple that I wanted to read out, Luciano Fuentes says , “I'm not really sure why the “designers should know how to code” tweet caused such a stir. It's like saying “interior designers should know how to tile a bathroom”. It's not necessary but it sure helps to understand your medium.”
Florent V says, “It seems to me that nobody has tried to teach graphic designers how to work for the web medium other than telling them: learn how to code stupid! I mean, there could be a 300-page book on the specificities on the medium for graphic designers. Not a “web design” book but a book which says what you can do and what you can’t, what the future possibilities look like, etc. And such a book shouldn’t be limited to the technical restrictions and possibilities, there would be other fields to cover (web marketing and web usability).” Wow! I don’t know how you would write that book, but I would sure love to see it. That would be an amazing accomplishment if you could communicate to designers in a designer’s language what the things you need to know before you design for the Web are. That would be amazing. Because I think Florent is right, the reason we tell people if you’re a web designer you really have to understand the code even if you don’t end up writing it yourself, the reason we do that is because we can’t find, we haven’t found a way to explain the Web as a medium, what you need to know as a designer, in any other terms other than well you just have to understand the code.
Florent V says , “It seems to me that nobody has tried to teach graphic designers how to work for the web medium other than telling them: learn how to code stupid! I mean, there could be a 300-page book on the specificities on the medium for graphic designers. Not a “web design” book but a book which says what you can do and what you can't, what the future possibilities look like, etc. And such a book shouldn't be limited to the technical restrictions and possibilities, there would be other fields to cover (web marketing and web usability).” 哇！ I don't know how you would write that book, but I would sure love to see it. That would be an amazing accomplishment if you could communicate to designers in a designer's language what the things you need to know before you design for the Web are. That would be amazing. Because I think Florent is right, the reason we tell people if you're a web designer you really have to understand the code even if you don't end up writing it yourself, the reason we do that is because we can't find, we haven't found a way to explain the Web as a medium, what you need to know as a designer, in any other terms other than well you just have to understand the code.
Stephan: I agree. I mean just pointing someone towards the code isn’t gonna help them understand what the Internet is as far as the design aspect of it, right. Just saying oh go look at the code behind that website is not gonna really help someone if they don’t understand the fundamentals of the screen and things like that. I completely agree with that point.
史蒂芬：我同意。 I mean just pointing someone towards the code isn't gonna help them understand what the Internet is as far as the design aspect of it, right. Just saying oh go look at the code behind that website is not gonna really help someone if they don't understand the fundamentals of the screen and things like that. I completely agree with that point.
Kevin: Hmm, yeah. So yes, thank you everyone for that feedback, and we look forward to reading your feedback on today’s show. Let’s finish off with our host’s spotlights. Just a couple, so we better make them good Stephan.
凯文：嗯，是的。 So yes, thank you everyone for that feedback, and we look forward to reading your feedback on today's show. Let's finish off with our host's spotlights. Just a couple, so we better make them good Stephan.
Stephan: Alright. You want me to go first?
Stephan: Alright. You want me to go first?
Kevin: Yeah, what do you got?
Kevin: Yeah, what do you got?
Stephan: Well, I have Evom, which it’s a converter for movies. It’s for Apple users so we’ll just get that out there right now. It converts movies for iTunes for the Web actually; it actually converts to HTML5 format. I don’t really understand that yet but I’m gonna try it out. And then it also converts to like iPods, things like that, and makes them— It’s much simpler. There was another app out there that it’s no longer around anymore, and I can’t think of the name; I actually uninstalled it because I wasn’t using it because they stopped…
Stephan: Well, I have Evom , which it's a converter for movies. It's for Apple users so we'll just get that out there right now. It converts movies for iTunes for the Web actually; it actually converts to HTML5 format. I don't really understand that yet but I'm gonna try it out. And then it also converts to like iPods, things like that, and makes them— It's much simpler. There was another app out there that it's no longer around anymore, and I can't think of the name; I actually uninstalled it because I wasn't using it because they stopped…
Kevin: It’s VisualHub.
Kevin: It's VisualHub.
Stephan: VisualHub, yeah. Yeah. They’d stopped writing it, updating it, so I’ve been looking for something and I just happened to come across this link, so it’s called Evom, it’s fast, it’s quick, they seem to be on top of the feature, so go out there and check it out.
Stephan: VisualHub, yeah. 是的 They'd stopped writing it, updating it, so I've been looking for something and I just happened to come across this link, so it's called Evom, it's fast, it's quick, they seem to be on top of the feature, so go out there and check it out.
Kevin: Wow. The one I’m using at the moment is HandBrake, which is a free and open source and … it’s not pretty, let’s put it that way. But it does do nice things like DVD ripping, so you can put a commercial DVD in and if it’s the right region for your drive it will, by using a copy of VLC—so you have to also install the Videolan Player on your machine—HandBrake uses that to decode the DVD and will make videos that are suitable for iTunes as well. But it looks like Evom is way more polished and way more end user friendly.
凯文：哇。 The one I'm using at the moment is HandBrake , which is a free and open source and … it's not pretty, let's put it that way. But it does do nice things like DVD ripping, so you can put a commercial DVD in and if it's the right region for your drive it will, by using a copy of VLC—so you have to also install the Videolan Player on your machine—HandBrake uses that to decode the DVD and will make videos that are suitable for iTunes as well. But it looks like Evom is way more polished and way more end user friendly.
Stephan: And it’s free.
Stephan: And it's free.
Kevin: This is something – yeah, it’s free. There are plenty of options out there that will charge you $25 for this, but this is really nice. Looks like it converts YouTube videos as well?
Kevin: This is something – yeah, it's free. There are plenty of options out there that will charge you $25 for this, but this is really nice. Looks like it converts YouTube videos as well?
Stephan: Yeah, it’ll pull them down and convert them; you just give it the URL.
Stephan: Yeah, it'll pull them down and convert them; you just give it the URL.
Kevin: Wow, that’s very sweet. I’m not sure my spotlight can stand up to that, but it is one that will work on Windows, so it’s got that going for it. What I have to suggest is Dummyimage.com which is the dynamic dummy image generator. When you’re laying out a site, maybe it’s a wireframe or you’re just creating the skin, the outline of what your site will look like, you know when you put in text you generally use a site like Lipsum.com to generate Lorem Ipsum text, the nonsense text that will fill paragraphs so you can see sort of what the page layout will look like, well you need the same thing for your images. Maybe you’re putting ad spots down the right hand side like we have at SitePoint, and you don’t actually have the ads but you need some placeholder images that will just show those dimensions and what’s gonna go there. Well this site will generate those for you on the fly. You go to Dummyimage.com and you fill in a little form with the dimensions of the image you want, the background color you want, the foreground color you want, and optionally some text that you want in the image. So if it’s a placeholder for an advertisement you might write ‘advertisement’ in there as the text. And what it gives you is a URL that will dynamically generate a filler image, and then you just put in your page layout, you put an image tag pointing to that URL and you will get that placeholder image. If you don’t specify any text by default it’ll just put like if it’s a 600 x 400 image it will have ‘600 x 400’ in an empty box. But these will save you a lot of time creating these filler images. I know when I’m laying out a page and I don’t have images to fill, I go “Ah well, I’ll have to open Photoshop and create a new canvas of the right size and put in some kind of text that indicates that there’s something here.” This automatically does it for you. You don’t actually have to generate and store the images on your server, you just point at these magic URLs, it’s really slick. So yeah. The next time you’re laying out a page tryout Dummyimage.com
Kevin: Wow, that's very sweet. I'm not sure my spotlight can stand up to that, but it is one that will work on Windows, so it's got that going for it. What I have to suggest is Dummyimage.com which is the dynamic dummy image generator. When you're laying out a site, maybe it's a wireframe or you're just creating the skin, the outline of what your site will look like, you know when you put in text you generally use a site like Lipsum.com to generate Lorem Ipsum text, the nonsense text that will fill paragraphs so you can see sort of what the page layout will look like, well you need the same thing for your images. Maybe you're putting ad spots down the right hand side like we have at SitePoint, and you don't actually have the ads but you need some placeholder images that will just show those dimensions and what's gonna go there. Well this site will generate those for you on the fly. You go to Dummyimage.com and you fill in a little form with the dimensions of the image you want, the background color you want, the foreground color you want, and optionally some text that you want in the image. So if it's a placeholder for an advertisement you might write 'advertisement' in there as the text. And what it gives you is a URL that will dynamically generate a filler image, and then you just put in your page layout, you put an image tag pointing to that URL and you will get that placeholder image. If you don't specify any text by default it'll just put like if it's a 600 x 400 image it will have '600 x 400' in an empty box. But these will save you a lot of time creating these filler images. I know when I'm laying out a page and I don't have images to fill, I go “Ah well, I'll have to open Photoshop and create a new canvas of the right size and put in some kind of text that indicates that there's something here.” This automatically does it for you. You don't actually have to generate and store the images on your server, you just point at these magic URLs, it's really slick. 嗯是的。 The next time you're laying out a page tryout Dummyimage.com
And that’s it for our podcast for two today, Stephan. Why don’t you signoff and let people know where you are.
And that's it for our podcast for two today, Stephan. Why don't you signoff and let people know where you are.
Stephan: Yep, you can find me on Twitter @ssegraves and you can read my blog at badice.com.
Stephan: Yep, you can find me on Twitter @ssegraves and you can read my blog at badice.com .
Kevin: And you can follow me on Twitter @sentience and SitePoint @sitepointdotcom. Join us next week for the second half of our interview with Derek Powazek about community. You can visit the SitePoint Podcast at sitepoint.com/podcast to leave comments on the show and to subscribe to get every show automatically.
Kevin: And you can follow me on Twitter @sentience and SitePoint @sitepointdotcom . Join us next week for the second half of our interview with Derek Powazek about community. You can visit the SitePoint Podcast at sitepoint.com/podcast to leave comments on the show and to subscribe to get every show automatically.
The SitePoint podcast is produced by Carl Longnecker and I’m Kevin Yank. Thanks for listening. Bye, bye.
The SitePoint podcast is produced by Carl Longnecker and I'm Kevin Yank. 谢谢收听。 Bye, bye.
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.
谢谢收听！ 欢迎使用下面的评论字段让我们知道我们的状况，或者继续讨论。
翻译自: https://www.sitepoint.com/podcast-53-im-here-with-the-booze/
