SitePoint播客＃130：快速响应设计

Episode 130 of The SitePoint Podcast is now available! This week the panel is made up of Louis Simoneau (@rssaddict), Brad Williams (@williamsba), Stephan Segraves (@ssegraves and Patrick O’Keefe (@ifroggy).

SitePoint Podcast的第130集现已发布！本周的座谈会由Louis Simoneau( @rssaddict )，Brad Williams( @williamsba )，Stephan Segraves( @ssegraves和Patrick O'Keefe( @ifroggy ))组成。

下载此剧集 (Download this Episode)

You can download this episode as a standalone MP3 file. Here’s the link:

您可以将本集下载为独立的MP3文件。这是链接：

SitePoint Podcast #130: High on Responsive Design (MP3, 41:36, 38.2MB)

SitePoint Podcast＃130：高响应设计 (MP3，41:36，38.2MB)

剧集摘要 (Episode Summary)

Here are the topics covered in this episode:

以下是本集中介绍的主题：

Boston Globe’s new Responsive design

波士顿环球报的新响应式设计
How to Report Browser Bugs

如何报告浏览器错误
Node.js Knockout Winners Revealed

Node.js淘汰赛获奖者揭晓
Introducing Twitter Analytics

推特分析介绍
Google Aims Dart To Kill JavaScript

Google瞄准Dart杀死JavaScript

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

浏览http://delicious.com/sitepointpodcast/130中显示的参考链接的完整列表。

主持人聚光灯 (Host Spotlights)

Brad: The Evolution Of The Web

布拉德：网络的演变
Patrick: Back4TheFuture.com – Nike Shoes for Michael J Fox Foundation

帕特里克(Patrick)： Back4TheFuture.com – Michael J Fox Foundation的耐克鞋
Louis: FitVids.js

路易斯： FitVids.js
Stephan: Bubble Boys

斯蒂芬：泡泡男孩

面试成绩单 (Interview Transcript)

Louis: Hi everyone, thanks for downloading this episode of the SitePoint Podcast, just wanted to drop in a quick note to remind you all that we’ve yet again been nominated this year in the .net Magazine Awards for Podcast of the Year.

路易斯：大家好，感谢您下载这一集的SitePoint播客，只是想简短地提醒大家，我们今年仍再次获得《 .net杂志》年度播客奖提名。

Patrick: Yeah!

帕特里克：是的！

Stephan: Woo-hoo!

史蒂芬：呜呜！

Patrick: Please vote.

帕特里克：请投票。

Louis: Yeah, absolutely. So just wanted to tell everyone that if you haven’t voted yet now is the time because the voting for the preliminary round closes on September 30th, so this is our last panel show before the voting closes, so go to thenetawards.com, cast your votes for SitePoint in the Podcast category and any of your other favorites in all the other categories. Thanks very much, now on to the show. Hello and welcome to another episode of the SitePoint Podcast, this week is another news and commentary show with a regular panel, how’s it going guys?

路易斯：是的，绝对。因此，我想告诉大家，现在是时候开始投票了，因为初选投票将于9月30日截止，所以这是投票截止之前我们的最后一次小组讨论，因此请前往thenetawards.com，演员表您在Podcast类别中对SitePoint的投票，在所有其他类别中对其他收藏夹的投票。非常感谢，现在来看节目。您好，欢迎收看SitePoint播客的另一集，本周是另一场定期面板新闻和评论节目，大家好吗？

Brad: Howdy.

布拉德：你好。

Stephan: Pretty good, how are you?

斯蒂芬：很好，你好吗？

Patrick: It’s going good, just got back from Los Angeles where I hung out with Ted S from the SitePoint Forums, Ted Sindzinski, had a lot of fun and, yeah, he’s been around for a long time like me, so it’s good to swap stories with another old-timer.

帕特里克(Patrick)：一切都很好，刚从洛杉矶回来时，我和SitePoint论坛的Ted S在一起，Ted Sindzinski很开心，是的，他和我一样已经存在很长时间了，所以对与另一位老朋友交换故事。

Louis: Awesome, sounds good.

路易斯：太好了，听起来不错。

Brad: Grand old man of the forum.

布拉德：论坛的老人。

Patrick: Yeah, much like Brad and Stephan also old men of the SitePoint Forums, that should be a calendar shoot, the old men of the SitePoint Forums (laughter).

帕特里克(Patrick)：是的，就像布拉德(Brad)和斯蒂芬(Stephan)一样，也是SitePoint论坛的老头，应该是个日历拍摄，SitePoint论坛的老头(笑)。

Louis: That sounds terrible, I think we would sell like — we would see seven copies of that.

路易斯：听起来很糟糕，我想我们会这样出售-我们会看到其中的七个副本。

Brad; They’d pay us not to make that contentalendar!

布拉德 他们会付钱给我们，不要让这个满足感！

Stephan: We’d sell seven copies to our mothers.

斯蒂芬：我们会卖给母亲七本。

Patrick: I’d buy one, not hang it up mind you, but store it.

帕特里克(Patrick)：我会买一个，不要把它挂在心上，而是要存放起来。

Louis: Awesome. So there’s a bit of news this week, the story I had was pretty interesting to anyone who follows web design and who’s been following the podcast for the past couple of months, we’ve been talking a lot about responsive web design as a sort of concept, when I interviewed Jeremy Keith we talked about it, back when I had the authors of our mobile book, Myles Eftos and Max Wheeler on the show we talked about responsive web design, had Chris Coyier on a couple of weeks ago, he’s just done a redesign of his site that’s ultra-cool and responsive and has a search box that zips around the screen when you resize the page, which we’re all big fans of. But it’s still pretty much a technique that has stuck to sort of the little agency sites or blogs or personal sites of web designers trying to demo out this technology, at least until now. I think yesterday The Boston Globe just launched a brand new site, it’s not even a redesign it’s a brand new site, which is I guess the first really mainstream website that’s going to get a lot of traffic that has one of these responsive designs that displays beautifully really whatever the dimensions of your browser or device are.

路易斯：太好了。因此，本周有一些新闻，我的故事对于所有关注Web设计并且在过去几个月一直关注播客的人来说都非常有趣，我们一直在谈论响应式Web设计，这是一种概念，当我采访杰里米·基思(Jeremy Keith)时，我们就谈到了这一点，而当我们在移动电视的作者Myles Eftos和麦克斯·惠勒(Max Wheeler)上参加了我们谈论响应式网页设计的展览时，克里斯·科耶尔(Chris Coyier)就在几周前对他的网站进行了重新设计，该网站非常酷，响应速度快，并且在您调整页面大小时有一个搜索框可以在屏幕上滑动，我们都是我们的忠实拥护者。但这至少仍然是一种技术，一直停留在试图演示这种技术的小型代理商站点，博客或Web设计人员的个人站点上。我想昨天《波士顿环球报》刚刚推出了一个全新的网站，它甚至没有经过重新设计，而是一个全新的网站，我想这是第一个真正的主流网站，该网站将获得很多流量，其中包含展示这些响应设计之一无论您的浏览器或设备的尺寸如何，都非常漂亮。

Patrick: Yeah, I’ve never done any drugs (laughter), and I never will, but —

帕特里克：是的，我从来没有做过任何毒品(笑声)，而且我也从未做过，但是-

Brad: I don’t know where you’re going with this.

布拉德：我不知道你要去哪里。

Louis: I wonder where this is going.

路易斯：我想知道这是怎么回事。

Patrick: Let me finish. I think that as I open and scroll this and I watch the sun jump around, just watch the sun and watch different things, I think I would have to believe that this is kind of what it’s like to be on drugs watching this text jump around like this (laughter), like I’m high right now just looking at this website.

帕特里克：让我结束。我认为，当我打开并滚动此按钮时，我会看着太阳跳来跳去，只是看着太阳并看着不同的事物，我想我必须相信，这就像在毒品上观看这种文本跳来跳去的感觉一样像这样(笑声)，就像我现在在浏览此网站时很高。

Brad: Managed way to read, I think it’s great, I love it, I’ve seen a lot of chatter on Twitter about it too, and I’ve got to say this is one of the bigger sites that’s actually done a redesign or relaunch and people have liked it; typically it seems like when these really popular and large sites do this the immediate first reaction is “it sucks, I hate it, blah, blah, blah, go back to the old way, you know, people don’t like change.

布拉德(Brad)：一种易于管理的阅读方式，我认为这很棒，我喜欢它，我也在Twitter上也看到了很多这样的话题，我必须说这是实际上经过重新设计或设计的较大型网站之一重新启动，人们喜欢它；通常，当这些真正受欢迎且规模较大的网站这样做时，第一眼的React是“糟透了，我讨厌它，等等，等等，回到旧的方式，你知道，人们不喜欢改变。

Patrick: I hate to be that guy, but is it because you listen to the web development audience, Brad, you listen to a lot of developers who are just like “oh, wow, it’s out there, responsive design!”?

帕特里克(Patrick)：我讨厌成为那个家伙，但这是因为您在听Web开发的受众，布拉德(Brad)，您在听许多开发人员，就像“哦，哇，它在那里，响应式设计！”？

Brad: Well, it was moreso — a lot of it was responsive design but it was also just the cleanliness, and it’s like a lot of new sites have this problem, it’s so much content it can be overwhelming, and I don’t think anyone’s perfected that art of how to give out a lot of content without it being overwhelming or too cluttered or just over the top. This Boston Globe site’s pretty good, and the fact that it’s responsive just really puts it over the top, I mean I think it’s a great site; they did a really good job.

布拉德：嗯，还可以，很多都是响应式设计，但也很整洁，就像很多新网站都存在这个问题，内容太多，可能会让人不知所措，我认为任何人都可以完美地展现出大量内容而又不至于变得太杂乱或太杂乱或刚好超过顶部的艺术。这个波士顿环球报的网站相当不错，而且它的响应能力确实使它排在首位，我的意思是我认为这是一个很棒的网站。他们做得很好。

Louis: Yeah, it’s interesting, I mean I think from my understanding is that this is not actually a redesign, it’s a brand new site, right; Boston Globe used to have, or still has a site called Boston.com which many people would be familiar with, a sort of mix of blogs and some content from the newspaper that’s very popular, they do the big picture blog that I’m a big fan of anyway, a photography blog. But this was an attempt to launch something that’s a little bit more focused on the text content from the newspaper, it’s going to be a subscription model that’s I think something like three or four dollars a week, so probably pretty similar to the price of the newspaper. And I guess they’re going the angle of because it’s responsive you can view on any device be it a phone or tablet or whatever, so this is going to kind of take the place of the subscription app that other news outlets like say the New York Times have gone in the way of monetizing their content for say the iPad or iPhone.

路易斯：是的，很有趣，我的意思是我认为我认为这实际上不是重新设计，而是一个全新的网站，对吧？波士顿环球报曾经拥有或仍然有一个名为Boston.com的网站，很多人会熟悉这种网站，其中包括博客和报纸上一些非常受欢迎的内容的混合，他们做的是大图片博客，不管怎么说，摄影博客还是个大粉丝。但这是一种尝试，目的是要推出一种更侧重于报纸文字内容的东西，这将是一种订阅模式，我认为这大约是每周三到四美元，因此可能与报纸的价格非常相似。报纸。而且我想他们正在考虑这个问题，因为它具有响应性，您可以在手机，平板电脑等任何设备上观看，因此这将取代其他新闻媒体(例如“新”)的订阅应用《纽约时报》采用了iPad和iPhone等内容获利的方式。

Patrick: Yeah, and we spoke about this in a recent episode, that was one of the things that I found most interesting about it is the development, it increases the development, but also the development that it eliminates that a lot of brands and companies might have had to do before like a mobile app, where now it’s just a part of the native website, and I think it’s interesting to see that play out and so soon especially with such a big brand and a big content company like The Boston Globe.

帕特里克：是的，我们在最近的一集中谈到了这一点，这是我发现最有趣的一件事，即发展，它促进了发展，但也消除了许多品牌和公司可能以前需要像移动应用程序那样做，现在它只是本机网站的一部分，我认为有趣的是，看到这种情况并很快出现，特别是对于像《波士顿环球报》这样的大品牌和大内容公司而言。

Louis: Yeah, it’s really great and it’s also going to be interesting to see, I mean I don’t know if any of our listeners have been around for long enough to remember when table-based layout was just giving way to CSS for design, some of the big sites that went that route to begin with kind of paved the way for that to become a mainstream and just to become the way that web design is done, so if you think back to I think it was ESPN that was one of the first ones that did a table-less layout, and there are some others that I’m forgetting, but yeah, a lot of people at least in my Twitter stream seem to think that this is kind of a similar moment for responsive web design and that from now on if you’re doing a content website that’s not responsive you’re kind of old-school and doomed to the history bin of web design.

Louis：是的，这真的很棒，而且看起来也很有趣，我的意思是我不知道我们的听众是否已经存在了很长的时间，以至于无法记住基于表的布局只是让CSS进行设计时，从那开始的一些大型网站开始为成为主流并成为完成网页设计的方式铺平了道路，所以如果您回想一下，我认为正是ESPN就是其中之一第一个使用无表格布局的布局，还有一些我忘记了，但是，是的，至少在我的Twitter流中，很多人似乎认为这是响应式Web的类似时刻设计，从现在开始，如果您创建的内容网站没有响应，那么您就有点老套，并且注定要关注网页设计的历史记录了。

Patrick: So was The Boston Globe paywall before this launch or is this a new thing for them?

帕特里克(Patrick)：那么，在发布之前，《波士顿环球报》的付费专区还是对他们来说是新事物？

Louis: I think it’s an entirely new thing is my understanding is that Boston.com is a different thing where they were just trying to be an ad supported online presence that included a bunch of blogs and content that was outside of the newspaper, and this is an attempt to do a real sort of newspaper site that exists as a paywall thing.

路易斯：我认为这是一个全新的事物，我的理解是，Boston.com是另一回事，他们只是试图成为广告支持的在线形象，其中包括大量博客和报纸之外的内容，试图做一种真正的报纸网站，作为付费专区存在。

Patrick: Yeah, it’s interesting because when we, us four, put our ear to the ground obviously a lot of that is influenced by development types. I don’t know what the general consumer reaction is to the paywall, right, because I think that’s the area that they would go to more is that there’s a new paywall for Bostonglobe.com website. So I don’t know if that’s something that has received any pushback or any criticism, because obviously paywalls have been criticized a lot in the past with different outlets, so I don’t know if The Boston Globe is going to avoid that here.

帕特里克：是的，这很有趣，因为当我们四岁的时候，我们的想法显然受到了开发类型的影响。我不知道一般消费者对付费专区有何React，是的，因为我认为他们会更关注的领域是Bostonglobe.com网站有了新的付费专区。因此，我不知道这是否受到了任何回击或批评，因为显然过去在使用不同的渠道对付酬墙进行了很多批评，所以我不知道《波士顿环球报》是否会在这里避免这种情况。

Louis: To me what it seems more like is it’s comparable like I was saying with some of the subscription based apps that other news outlets have launched for the various platforms, right, so you can get the New York Times app for your iPad and that costs a fixed amount and you get the New York Times on your iPad. What they’ve tried to do here, and it’s kind of an ambitious play, is to leverage the idea of responsive web design and say look if we can make one website that works on any device and you get one subscription that gives you access to all of that, so the paywall content on your desktop is the same as the tailored content on your iPad, and when you load it on the iPad you get a really nice sort of two-column view that really looks like it was designed for that screen size and similarly if you look at it on your phone. So they want sort of to replace the paywall app with the web based paywall, and maybe that will work with consumers because people have come to the understanding that it is okay to pay for content on those devices as long as it looks like it was tailored for those devices; like I wouldn’t pay to access the New York Times website on the iPad because it just — I have to zoom around all the time because it’s not designed for that kind of screen, but I would pay for the app because it’s a really pleasant and easy reading experience.

路易斯：对我来说，它看起来更像是可比的，就像我在与其他基于订阅的应用程序说的那样，其他新闻媒体已经针对各种平台推出了，对，所以您可以在iPad上获得《纽约时报》应用程序，费用固定，您可以在iPad上获得《纽约时报》。他们在这里尝试做的事情是一项雄心勃勃的尝试，就是利用响应式网页设计的想法，并说一下我们是否可以使一个网站在任何设备上都能正常工作，并且您获得一个可以访问以下内容的订阅：所有这些，因此桌面上的付费专区内容与iPad上的定制内容相同，当您将其加载到iPad上时，您会得到一种非常不错的两栏视图，看起来像是专为该视图设计的屏幕尺寸，如果您在手机上查看屏幕尺寸也是如此。因此，他们希望用基于Web的Paywall替换paywall应用，这也许对消费者有用，因为人们已经理解，只要看起来像量身定制，就可以为那些设备上的内容付费。对于那些设备；就像我不会因为在iPad上访问《纽约时报》网站而付费一样，因为它–我必须一直进行缩放，因为它不是为那种屏幕设计的，但是我会为该应用程序付费，因为它的确令人愉快和轻松的阅读体验。

Stephan: Do you know if the, I guess the website; does it use HTML5 so they can cache the content?

斯蒂芬：你知道那是我的网站吗？它使用HTML5以便他们可以缓存内容吗？

Louis: That’s a great question; I do not know the answer to that. I can probably find out relatively quickly.

路易斯：这是一个很好的问题。我不知道答案。我大概可以很快找到。

Stephan: The reason I ask is because you know that’s one of the big pluses for me for the New York Times is that I can download a bunch of articles before let’s say I get on an airplane or get on a train and I can read it on a train, so if they’re not offering that to me I’m not going to pay because that’s usually when I’m reading is on the plane or going somewhere.

斯蒂芬：我问的原因是因为您知道《纽约时报》对我来说是一大好处，是我可以下载很多文章，然后再说我上飞机或上火车，然后我才能阅读在火车上，所以如果他们不提供给我，我就不会付款，因为通常这是我在飞机上读书或去某处的时候。

Louis: Yeah, right, that’s a really good point, I don’t see an obvious like cache manifest kind of thing, so I guess the app might have that advantage in that it’s really — it works offline really well. But it will be really interesting to see how this works going forward and the effect that it has on other sites’ willingness to embrace the kind of responsive web design instead of paying for a bunch of separate apps on different platforms.

Louis：是的，这是一个很好的观点，我看不到类似缓存清单这样的东西，所以我猜该应用程序可能具有这样的优势，那就是它确实可以脱机工作。但是，看到它如何进行下去，以及它对其他网站采用响应式网页设计而不是在不同平台上购买大量独立应用程序的意愿产生的影响，将是非常有趣的。

Patrick: Right.

帕特里克：对。

Louis: Yeah, but I mean one thing we all have to agree is that it is a really pretty looking website and the way they’ve done some of the challenges of responsive design, so if you look when you’re looking at it full screen you’ve got to sort of hover over the menu items and then you get this big dropdown with the subsections, but then when you’re looking at it in a narrow window you’ve just got a one-sections thing which doesn’t have a hover because I’m assuming they’re expecting most people looking at it on a screen that size will be using touch devices and when you tap on it then you get all the subsections sort of appear below it, so ways of dealing with like big menus that are hard to cram into a small amount of space they’ve collapsed it really nicely, and it may not have the search box zooming around the screen like Chris Coyier’s site.

路易斯：是的，但是我的意思是我们所有人都必须同意的是，这是一个非常漂亮的网站，而且他们已经完成了响应式设计的一些挑战，因此，如果您看的是完整的网站，屏幕上，您必须将鼠标悬停在菜单项上，然后使用小节显示此大下拉菜单，但是当您在狭窄的窗口中查看时，您只会看到一个单节的内容，不用悬停，因为我假设他们期望大多数人在屏幕上看到它会使用触摸设备，并且当您点击它时，所有小节都会显示在它的下面，所以处理方式像大型菜单一样，它们很难塞入少量空间，因此它们确实折叠得很好，而且可能没有Chris Coyier的站点那样使搜索框在屏幕上放大。

Brad: Boo.

布拉德：嘘

Louis: (Laughs)

路易斯：(笑)

Brad: If the search box isn’t flying then I’m definitely not paying.

布拉德：如果搜索框没有运行，那么我肯定不会付款。

Patrick: This site isn’t as trippy as the last one (laughter), but it’s still trippy.

帕特里克(Patrick)：这个网站不如上一个(笑声)那样令人迷惑，但仍然令人迷失。

Stephan: I’ll say this, I think it looks good, I think especially as it’s smaller I think it looks good, full screen on my laptop here I don’t know, I don’t know if it feels like a news website to me, I guess that’s my only complaint, it doesn’t feel like a newspaper, I don’t know what the means, like I don’t know what a newspaper is supposed to feel like.

斯蒂芬：我要说的是，我认为它看起来不错，尤其是因为它较小时，我认为它看起来不错，我在笔记本电脑上全屏显示，我不知道，我不知道它是否像新闻网站对我来说，我想这是我唯一的抱怨，感觉不像是报纸，我不知道用什么手段，就像我不知道报纸应该是什么样。

Brad: Maybe they didn’t want it to feel like a newspaper.

布拉德：也许他们不想让它看起来像报纸。

Stephan: Yeah, you know what, Brad, I don’t need sarcasm (laughter). But other than that I really like the way it looks on a smaller screen because it’s very easy to navigate so I like that.

斯蒂芬：是的，你知道吗，布拉德，我不需要讽刺(笑声)。但是除此之外，我真的很喜欢它在较小屏幕上的显示方式，因为它非常易于浏览，所以我很喜欢。

Patrick: So I found this story through Forbes.com and it is a blog post on the Twitter Developer blog introducing Twitter web analytics, and what I gather from this post is that Twitter will soon be releasing for all website owners over the next few weeks a way to track what traffic you’re generating through Twitter, how many clicks you’re getting from Tweets, how many Tweets there are that mention your website, the effectiveness of the Tweet button if you use it, and more like your most popular content, from a special dashboard that you’ll be able to access through the Twitter website, sort of like Google webmaster tools I would say in how they allow you to view your rank in various Google search terms and see whether they can spider you and all those things. It looks like Twitter is going to roll out something like that, and a small pilot group of testers have access to it now but the rest of us, large and small, should be getting access to it in the next few weeks.

帕特里克(Patrick)：所以我在Forbes.com上找到了这个故事，这是Twitter开发人员博客上的博客文章，介绍Twitter Web分析，而我从这篇文章中学到的是，Twitter将在未来几周内为所有网站所有者发布。一种跟踪您通过Twitter产生的流量，从Tweets获得的点击次数，提及您的网站的Tweets的数量，Tweet按钮(如果使用)的有效性以及更像最受欢迎的按钮的方式内容，从可以通过Twitter网站访问的特殊仪表板，类似于Google网站站长工具，我会说它们如何允许您以各种Google搜索条件查看排名，并查看它们是否可以为您和所有这些东西。看起来Twitter将会推出类似的东西，一小群测试人员现在可以使用它，但是我们其余的人，无论大小，都应该在接下来的几周内对其进行访问。

Louis: Yeah, this looks really good. I’m definitely looking forward to this because it’s something that if you use sort of a social media analytics tool, or social media sharing tool like Share This or Add This, those come with some built-in analytics, the analytics aren’t great, and it also means if someone Tweets a link to your thing not from that button you don’t get the tracking on it, so is something that I think would be really useful for any kind of website owner that wants to be able to track how many people are clicking on stuff from their Tweets.

路易斯：是的，这看起来真的很好。我绝对很期待这一点，因为如果您使用某种社交媒体分析工具或“共享本”或“添加本”之类的社交媒体共享工具，这些工具附带一些内置分析功能，这些分析就不是很好，这也意味着，如果有人通过推特(而不是从该按钮)链接到您的事物，则您不会对其进行跟踪，对于那些希望能够跟踪的任何类型的网站所有者，这都是非常有用的有多少人点击其推文中的内容。

Patrick: Yeah, and as I look at this I can’t help but think about bit.ly and if they’re going to become the next service that the Twitter main website goes after because it might already be built-in in some way that you can get traffic for the specific links that you Tweet, since I do see a content tab in this screen grab, but either way it’s something that you could certainly Twitter rolling out at some point is — since they’re already shortening the URLs with t.co the only real issue is the custom URLs, but Twitter has shown before that it’s willing to go into certain markets where developers have already built up good presences, so I don’t know if I’m saying to be worried but I can definitely see them going there.

帕特里克(Patrick)：是的，就我而言，我忍不住想一想bit.ly，以及它们是否将成为Twitter主网站所追求的下一个服务，因为它可能已经以某种方式内置因为您确实在此屏幕抓取中看到了一个内容选项卡，所以您可以获取有关Tweet特定链接的访问量，但是无论哪种方式，您都可以肯定Twitter会在某个时候推出-因为它们已经缩短了URL使用t.co时，唯一真正的问题是自定义URL，但Twitter之前已经表明，它愿意进入开发人员已经建立良好影响力的某些市场，所以我不知道我是否在担心，但是我绝对可以看到他们去那里。

Louis: Well, I just think it makes a lot more sense for this stuff to be handled by Twitter than by a third party, like for me if I’m posting content to Twitter I’m okay with relying on Twitter to still be around for that content to continue existing, but if I have to also rely on a third party to shorten the URL and then track all my stuff which is independent of Twitter, especially in the case of bit.ly who are on a top-level domain which is let’s just say —

路易斯：嗯，我只是认为将这些内容由Twitter处理比由第三方处理更为有意义，例如对于我来说，如果我在Twitter上发布内容，我可以依靠Twitter仍然存在使该内容继续存在，但是如果我还必须依靠第三方来缩短URL，然后跟踪独立于Twitter的所有内容，尤其是在顶级域中的bit.ly的情况下我们只能说-

Patrick: Completely safe!

帕特里克：完全安全！

Louis: (Laughs) Let’s go with that, alright, so the CCTLD of bit.ly is totally secure, it’s in the most politically stable country in the world so we never have to worry about that, but yeah, for me like it makes sense for the URL to be shortened on Twitter because that’s where I’m putting the content.

路易斯：(笑)让我们一起去，好吧，所以bit.ly的CCTLD绝对安全，它位于世界上政治上最稳定的国家，所以我们不必为此担心，但是，对，因为我喜欢它在Twitter上缩短URL的意义，因为那是我要放置内容的地方。

Brad: Isn’t that kind of putting all your eggs in one basket though?

布拉德：那不是把所有的鸡蛋都放在一个篮子里吗？

Louis: But you’re putting all your eggs in one basket anyway, right, because if Twitter goes away the link isn’t there anyway, right?

路易斯：但是你还是把所有的鸡蛋都放在一个篮子里，对，因为如果Twitter消失了，那么链接就不存在了，对吗？

Brad: Well, I mean so you don’t share shortened links on any other service except for Twitter?

布拉德：嗯，我的意思是说，您不共享除Twitter以外的任何其他服务上的缩短链接吗？

Louis: No, why would you have to? No one else has a stupid 140 character limit (laughs).

路易斯：不，你为什么要这么做？没有人有一个愚蠢的140个字符限制(笑)。

Brad: Yeah, I mean I’ve actually gotten in the habit of sharing short links for the fact that it does give you those analytics, so if you’re sharing those links across rather than just pasting a link wherever it may be you’re still getting that quick traffic and you can kind of see is this effective or whatever, you know, even if you share wherever it may be I try to keep the links consistent. And, you’re right, I don’t share too often outside of Twitter maybe even Facebook, but when I do it’s typically I take that same URL that was shortened via Twitter and I’ll kind of pass it around because then I can track those stats.

布拉德：是的，我的意思是说我实际上已经习惯了共享短链接，因为它确实为您提供了这些分析，因此，如果您正在共享这些链接，而不仅仅是将链接粘贴到任何地方，那么您就可以了。仍然能获得如此快速的点击量，您可以看到这是有效的，还是知道，即使您在任何地方分享，我都尽力保持链接的一致性。而且，您是对的，我在Twitter之外甚至在Facebook上分享的次数都不多，但是当我这样做时，通常会使用通过Twitter缩短的网址，然后将其传递出去，因为这样我可以跟踪这些统计信息。

Louis: I guess that’s a good point.

路易斯：我想那是一个好点。

Patrick: That’s a good point. And I can see that being a reason that maybe Twitter doesn’t go the full route, and maybe bit.ly still has a good business with The Pro or obviously there are other tools that allow you to do that, some that you host yourself; for sure I use like using that Illiums, whatever it is, the short URL.

帕特里克：很好。而且我可以看到，这可能是Twitter不能完全解决问题的原因，也许bit.ly与The Pro仍然有良好的业务往来，或者显然还有其他工具可以帮助您做到这一点，其中一些您可以自己托管; 当然，无论使用什么，我都会像使用Illiums一样使用短网址。

Brad: It’s not that short.

布拉德：还不算短。

Patrick: (Laughs) Yeah, I’ve got iFrog.gy that I have not yet rolled out, so maybe one day.

帕特里克：(笑)是的，我有iFrog.gy，但我还没有推出，所以也许有一天。

Louis: Yeah, I still think that that’s probably the best solution for anyone who’s really serious about this, if you have the technical ability and you can register your own shortened domain then doing it yourself.

Louis：是的，我仍然认为，对于那些对此非常重视的人来说，这可能是最好的解决方案，如果您具有技术能力并且可以注册自己的缩短域名，然后自己动手做。

Patrick: Right.

帕特里克：对。

Louis: And I remember it was some time ago Tantek Çelik wrote this piece about coming up with a way of shortening links in an algorithmically reversible way so that you wouldn’t necessarily look up a database but you could just expand out the — was that more like just compressing the string of the URL? I don’t know if that’s making sense to anyone.

路易斯：我记得有一段时间，TantekÇelik写过这篇文章，提出了一种以算法可逆的方式缩短链接的方法，这样您就不必查找数据库，而只需扩展数据库即可。更像只是压缩URL的字符串？我不知道这对任何人都有意义。

Stephan: That makes sense, smart URLs.

史蒂芬：这很有意义，智能网址。

Louis: Yeah, so a way that even if the service goes away you can still use the algorithm to figure out what the original links were. So I don’t know, I mean I can’t say that I think doing it yourself is the best way, but then obviously no one can be bothered, and you know Twitter is probably a pretty safe bet for this, and it’s great that they’ve got analytics now, I think that’s going to be really useful.

路易斯：是的，即使服务消失了，您仍然可以使用该算法找出原始链接是什么。所以我不知道，我的意思是我不能说我认为自己做是最好的方法，但是显然没有人可以打扰，而且您知道Twitter可能是一个相当安全的选择，这很棒他们现在已经有了分析功能，我认为这将非常有用。

Brad: Alright, next up is the Node Knockout which is the annual Node.js Hackathon has announced their winners for the competition this year, this is actually the second year they’ve hosted this event, and it’s grown quite a bit. So this year they had 320 teams with more than 700 individuals competing, and that’s up from 100 teams last year with 250 participants. So basically what this competition is it’s a 48 hour hackathon building an application built on Node.js, which is if you’re not familiar with it it’s basically server side JavaScript environment which we’ve talked about a little bit recently and it seems to be certainly one of the buzzwords this year, and one of those technologies a lot of people are looking a little bit closer at, but I thought we could go through some of the winners and check out these apps because I mean these are pretty impressive apps for a 48 hour build.

布拉德：好吧，接下来是Node Knockout，这是一年一度的Node.js Hackathon宣布了今年的比赛优胜者，这实际上是他们举办该赛事的第二年，并且增长了很多。因此，今年他们有320个团队，有700多人参加比赛，而去年有100个团队，有250名参与者。因此，基本上，这场竞赛是一个48小时的黑客马拉松，构建基于Node.js的应用程序，也就是说，如果您不熟悉它，那基本上是服务器端JavaScript环境，我们最近已经讨论了一点，而且似乎无疑是今年的流行语之一，而很多人正在密切关注其中的一项技术，但是我认为我们可以通过一些获奖者来检查这些应用程序，因为我的意思是这些应用程序非常令人印象深刻持续48小时。

Louis: Yeah, this stuff looks pretty cool.

路易斯：是的，这些东西看起来很酷。

Brad: Yeah, so the first winner, overall winner and solo winner category, I don’t know if that’s two categories or one, but it is Observer and the website is Observer.no.de, some of these sites are public apps so you can actually login to them and to play with others you just have to go into Git if it’s available and check out the source. But Observer actually allows you to watch your application users in realtime and you can actually see what they’re doing on your website, so if a user’s on your website and they’re kind of stumbling around lost trying to find the registration button or something like that you can actually see that and you can initiate a chat, an anonymous chat with them, and say hey are you looking for the register button, it’s right over here, and you can help them out, it’s kind of an interesting application. I think the one that I thought was the most interesting and the most fun was the overall team winner and that was the eight bit beats, and basically this is a web app where you signup, you literally just type in your name and it drops you right into a collaborative social beat and melody sequencer so you can actually make tracks in realtime with multiple people throughout, so it’s kind of interesting; if you fire it up it literally has I think it was Super Mario or somebody running across the sequencer.

布拉德：是的，所以是第一个获胜者，总体获胜者和个人获胜者类别，我不知道这是两个类别还是一个类别，但是它是Observer，网站是Observer.no.de ，其中一些网站是公共应用程序，因此您实际上可以登录到他们并与其他人一起玩，您只需要进入Git(如果有)并查看源代码。但是Observer实际上允许您实时监视您的应用程序用户，并且您实际上可以看到他们在您的网站上所做的事情，因此，如果某个用户在您的网站上并且在某种程度上迷失了寻找注册按钮之类的东西像这样，您实际上可以看到并可以发起聊天，与他们进行匿名聊天，然后说嘿，您在寻找注册按钮吗？它就在这里，您可以为他们提供帮助，这是一个有趣的应用程序。我认为我认为最有趣，最有趣的是整个团队的冠军，那是八位拍子，基本上这是一个网络应用程序，您可以在其中注册，您只需键入您的名字，它就会丢弃您直接进入协作的社交节拍和旋律音序器，这样您就可以与多人实时实时跟踪，因此很有意思；如果按字面意义启动它，我是否认为它是Super Mario或有人在音序器中运行。

Patrick: Megaman.

帕特里克：洛克曼。

Brad: Megaman, that’s who it was, and you can actually drop beats, and I though of you, Patrick, when I saw this, you can drop whatever beats and tones and as a group you can try and come up with a song together, so it’s kind of a cool way to work with each other.

布拉德(Brad)：曼加曼(Megaman)，原来是这样，您可以放下节拍，而我，虽然我，帕特里克(Patrick)，当我看到此节拍时，您可以放下任何节拍和音调，作为一个小组，您可以尝试一起创作一首歌，所以这是一种很不错的合作方式。

Patrick: Yeah, gotta get Puttin’ on the Ritz into this somehow.

帕特里克(Patrick)：是的，一定要让Ritz上的Puttin'进入。

Brad: I would imagine. This reminds me of when Google came out with the guitar and in like one day people were recreating Led Zeppelin songs and passing links around, like I could see that turning into something like this. There’s also a Drive.in which is basically a YouTube battle party, I guess it’s similar to Chill.com or Turntable but for videos where you can actually — you basically battle back and forth on YouTube videos for a crowd of people who can then kind of vote on whether they like or do not like your video and can throw tomatoes at you, so.

布拉德：我想。这让我想起了Google出来吉他的那一天，就像有一天人们在重建Led Zeppelin的歌曲并传递链接，就像我看到的那样。还有一个Drive.in基本上是一个YouTube战役聚会，我想它类似于Chill.com或Turntable，但是对于实际上可以播放的视频，您基本上是在YouTube视频上来回战斗，因此有很多人可以他们喜欢还是不喜欢您的视频并可以向您投掷西红柿的投票权，因此。

Patrick: Ouch.

帕特里克：哎呀。

Brad: They’re all pretty fun apps, and the fact that some of the source is actually available is kind of cool. These apps, by entering they’re not considered open source apps, they’re only open source if the author wanted to make them open source, so not all the apps are actually available for download but some of them are.

布拉德：它们都是非常有趣的应用程序，并且某些资源实际上可用的事实有点酷。这些应用程序通过输入不被视为开放源代码应用程序，只有在作者希望将其设为开放源代码时，它们才是开放源代码，因此并不是所有的应用程序都可以下载，但有些可以下载。

Louis: Right. What’s interesting here is you can really see that all of these apps are sort of leveraging the strengths of Node.js and sort of going places where it’s been difficult to develop apps using traditional stAX, so it’s a lot of stuff that requires high concurrency and a lot of simultaneous connections that stay open to the website which is something that Node.js does really well and that other, you know, like if you had a Lamp Stack every connection is firing up your whole PHP binary and Apache binary in memory, so you’d end up using a lot of memory if you have a lot of people connected at the same time in a lot of concurring connections, but Node being really small and fast and good at handling that kind of thing is ideal for these kind of apps that involve sort of monitoring things or that feel kind of realtime over TCP, you know.

路易斯：对。有趣的是，您真的可以看到所有这些应用程序都在利用Node.js的优势，并且在某些地方很难使用传统的stAX开发应用程序，因此很多东西需要高并发性和大量并发连接保持打开状态，这是Node.js确实做得很好的，另外，您知道，例如，如果您有Lamp Stack，则每个连接都会在内存中触发整个PHP二进制文件和Apache二进制文件，因此，如果同时有很多并发连接的人同时连接，那么您最终将占用大量内存，但是Node的体积非常小，速度快，并且擅长处理此类事情，对于这类用户来说是理想的选择您知道涉及到某种监控内容或通过TCP感到实时的应用程序。

Brad: Another interesting thing, this website it’s actually Nodeknockout.com and if you go all the way to the bottom it actually tells you that this website is a massively multi-player website, and if you realize it as you click around in the background you actually have a little avatar on this website that will kind of follow your mouse and you can actually talk to everybody else that’s viewing the website, which when I saw that I was like that’s kind of cool, so it’s kind of a little hidden bonus in the website itself.

布拉德：另一个有趣的事情，这个网站实际上是Nodeknockout.com ，如果您一直走到最底端，它实际上告诉您该网站是一个大型多人游戏网站，并且您在后台单击时是否意识到了这一点。您实际上在该网站上有一个头像，可以跟随您的鼠标，并且您实际上可以与正在浏览该网站的其他每个人交谈，当我看到自己像这样很酷时，这有点隐藏的好处在网站本身中。

Louis: Yep.

路易斯：是的 。

Brad: Anyways, it’s fun so certainly check it out and I would imagine that we will probably see the amount of entries double next year over this year just as it did this year, so some really cool stuff coming out of it.

布拉德：无论如何，这很有趣，所以一定要检查一下，我想我们明年可能会看到今年的参赛作品数量与今年一样翻番，所以会有一些很酷的东西出现。

Louis: Yeah, it’s surprising to me to even realize that Node has been around that long because it feels to me like we just started hearing about it, and then when you said like it’s an annual Node.js competition it’s like what do you mean annual, it hasn’t even been around for a year, but I guess time flies and we’re already two years into this.

Louis：是的，令我惊讶的是，竟然意识到Node已经存在了那么长时间，因为我觉得我们刚刚开始听说它，然后当你说这是一年一度的Node.js竞赛时，这意味着你的意思。每年，甚至还没有一年，但是我想时间已经过去了，我们已经两年了。

Brad: Yeah, from 250 last year that’s over 700 people this year so it’s more than doubled it’s almost tripled, and it’s only going to go up from there, it seems like it’s really starting to catch on, like you said, we’ve talked about it a few times already on the podcast and I’m sure we’ll be talking about it quite a bit more.

布拉德：是的，从去年的250人增加到今年的700多人，是现在的两倍多，几乎是现在的三倍，而且它只会从那里上升，就像您说的那样，这似乎真的开始流行了，我们已经在播客上已经讨论过几次了，我敢肯定我们会谈论更多。

Patrick: As if I didn’t feel old enough already now Node.js is getting older (laughter).

帕特里克：好像我现在还不够老， Node.js越来越老(笑)。

Brad: The old man of JavaScript.

布拉德： JavaScript的老头。

Patrick: The travesty.

帕特里克：荒唐。

Stephan: And this all while Google aims to kill JavaScript (laughter), I mean come on guys. We talk about Node.js and now there’s an article in Information Week about Google wanting to start its development and pushing its own language.

史蒂芬：在Google旨在杀死JavaScript(笑声)的同时，我的意思是，伙计们。我们谈论Node.js，现在在信息周刊上有一篇关于Google希望开始其开发并推广自己的语言的文章。

Louis: So Google is trying to kill JavaScript is the TLDR of the story you’re about to link me to?

路易斯：所以Google试图杀死JavaScript，这是您要链接到我的故事的TLDR吗？

Stephan: So Google’s pushing to have Dart, which is the new name for Dash, on the Web and they want people to use it to develop web applications rather than JavaScript. In their words they say that JavaScript is an implementation of the ECMA standard but it’s fundamentally flawed and can’t be fixed at a speed that matches its development ambitions. So, I think it’s interesting.

斯蒂芬：所以Google一直在努力将Dart(Dash的新名称)发布到网络上，他们希望人们使用它来开发Web应用程序而不是JavaScript。用他们的话说，JavaScript是ECMA标准的实现，但是它从根本上来说是有缺陷的，无法以与其开发野心相匹配的速度进行修复。因此，我认为这很有趣。

Louis: It’s pretty harsh.

路易斯：这很严厉。

Stephan: Pretty harsh and it may be a failure in the end.

斯蒂芬：非常严厉，最终可能会失败。

Louis: Yeah, it doesn’t sound like that’s gonna pan out, I mean is this something — is this for front end stuff?

路易斯：是的，这听起来好像不会成功，我的意思是，这是东西-这是用于前端的东西吗？

Stephan: Yeah, it’s actually going to be based on ECMAScript as well, so it’s going to be — I guess they’re trying to jumpstart, jump ahead of JavaScript where JavaScript is now and take it from there, and they really want to see it replace JavaScript as the main language of web development on the open web platform, that’s their words not mine.

斯蒂芬：是的，它实际上也将基于ECMAScript，因此它将成为-我想他们正在尝试快速入门，超越现在JavaScript并从那里开始使用JavaScript，他们真的很想看看它取代了JavaScript作为开放式Web平台上Web开发的主要语言，这不是他们的话。

Louis: Wow.

路易斯：哇。

Stephan: So I don’t know. I don’t see this going over well, I see it kind of turning into just another one of those things that we hear about in another couple of months that —

史蒂芬：所以我不知道。我看不到一切进展顺利，我认为这只是在接下来的几个月中我们听到的另一件事-

Louis: Yeah, I mean this one’s kind of baffling because you’d have to get all the browser makers on board to be like oh yeah we’ll just ditch JavaScript and all the work we’ve put into developing our JavaScript engines and we’ll just use this new thing. And the other thing is it seems like it’s kind of giving — it would be giving Google a head start if they play into it, right, because Google will have already developed an engine and an interpreter that runs this new language really fast and then everyone else has to build one from scratch.

路易斯：是的，我的意思是莫名其妙，因为您必须让所有浏览器制造商都参与进来，就像是的，是的，我们将放弃JavaScript以及我们在开发JavaScript引擎方面投入的所有工作，只会用这个新东西。另一件事是，这似乎是一种付出—如果他们参与进来，这将为Google抢先一步，对，因为Google已经开发出了一种引擎和一个解释器，可以非常快地运行这种新语言，然后每个人否则必须从头开始。

Stephan: Yeah. So I don’t know, I mean if it’s based on the ECMA T39 standard does it need its own or most of these browsers now are they supporting ECMA out of the box?

斯蒂芬：是的。所以我不知道，我的意思是，如果它基于ECMA T39标准，是否需要它自己的浏览器或其中的大多数浏览器，它们是否开箱即用地支持ECMA？

Louis: Man, I have no idea, as soon as people start talking about ECMAscript standard you’ve totally walked off the deep end of what I’m able to comment on.

路易斯：伙计，我不知道，一旦人们开始谈论ECMAscript标准，您就完全摆脱了我有能力评论的内容。

Stephan: (Laughs) I’m just wondering if that’s what their goal is with this is to follow the ECMA script standard because they think that’s going to be in the browser. Or maybe they think that Google Chrome is going to be the only browser in the next three years.

斯蒂芬：(笑)我只是想知道这是否就是遵循ECMA脚本标准的目的，因为他们认为这将出现在浏览器中。或者，也许他们认为Google Chrome将成为未来三年中唯一的浏览器。

Louis: Yeah, maybe that’s it.

路易斯：是的，也许就是这样。

Stephan: (Laughs)

斯蒂芬：(笑)

Brad: Yeah, I would be shocked, I mean you know JavaScript not only from the browser standpoint but also from the developer standpoint, I mean it’s been around a long time and there’s a lot of developers out there and there’s a lot of really passionate developers. It’s certainly not perfect, I don’t think any language really is, but you’re right, who knows, we might be eating our words in a year from now, but it would definitely take a huge push and some big names to get behind something like this for there even to make a dent to where people actually start discussing it on a regular basis.

布拉德：是的，我很震惊，我的意思是，您不仅从浏览器的角度而且从开发人员的角度都知道JavaScript，我的意思是已经存在了很长时间，并且那里有很多开发人员，而且确实有很多热情开发人员。这当然不是完美的，我不认为任何语言都是真的，但是你是对的，谁知道，从现在开始一年后我们可能会吃掉我们的话，但是肯定要花很大的力气和一些大人物甚至在这样的背后隐藏一些痕迹，甚至使人们无法真正开始定期讨论它。

Patrick: And the interesting part of the article for me was Brendon Eich, the creator of JavaScript and the Mozilla CTO is quoted in the article linking to a blog post that he wrote last month where he said that “many Googlers, especially the principles, do not like JavaScript and don’t believe it can evolve in time,” whatever that might mean, “and Google of course influences JavaScript evolution directly so they can put a finger on the scale here,” he says, “but they’re wrong and I’m glad at least some of the folks at Google working in TC39 actually believe in JavaScript, specifically its ability to evolve soon enough and well enough to enable both more predictable performance and programming in the large.” And he argued, according to the article here, that the slower development of the community driven standards is a necessary price to avoid fragmentation and to maintain interoperability, which makes sense to me; it’s one of those things that’s been around for a long time and, you know, I’m a non-developer but it’s — so many things I run are JavaScript that it would seem natural that it wouldn’t be going away any time soon. And the main problem I have with JavaScript is that you can turn it off in the browser (laughs), if you could just leave it on and not have it disabled that would be perfect because then you would always see my ads, greedy, greedy (laughter). So if Dart had to be on and you couldn’t disable it and I could serve ads through it I love it!

帕特里克(Patrick)：对我来说，有趣的部分是JavaScript和Mozilla CTO的创建者布伦登·艾希(Brendon Eich)，该文章引用了他上个月写的博客文章的链接，他说：“许多Google员工，特别是原则，他不喜欢JavaScript并且不相信它会随着时间的推移而发展，“这可能意味着什么，”而且Google当然会直接影响JavaScript的发展，因此他们可以在这里扩大规模，”他说，“但是错了，我很高兴至少有一部分在TC39工作的Google员工真正相信JavaScript，特别是JavaScript能够尽快足够好地发展以实现更可预测的性能和更大的编程能力。” 他认为，根据本文的文章，社区驱动标准的较慢开发是避免分散并保持互操作性的必要代价，这对我来说很有意义。这是已经存在很长时间的事情之一，而且，我不是开发人员，但事实是-我运行的很多东西都是JavaScript，因此很自然不会很快消失。我使用JavaScript的主要问题是您可以在浏览器中将其关闭(笑)，如果您可以将其保持打开状态而不禁用它，那将是完美的，因为那样的话您总是会看到我的广告，贪婪，贪婪(笑声)。因此，如果必须启用Dart而您不能禁用它，那么我可以通过它投放广告，我喜欢它！

Louis: Alright, I think we’ve just killed this story.

路易斯：好吧，我想我们只是扼杀了这个故事。

Patrick: Ah, man, dollar signs everywhere.

帕特里克：啊，男人，到处都有美元符号。

Stephan: Priorities there, Patrick, priorities.

史蒂芬：优先事项，帕特里克，优先事项。

Louis: You started off so well with like the community based standard is going to be a necessary condition for interoperability, you know you had me.

路易斯：您起步非常好，因为基于社区的标准将成为互操作性的必要条件，您知道您拥有我。

Patrick: Cha-ching! (Laughter)

帕特里克：茶青！ (笑声)

Louis: Yeah, so I guess it’s kind of a wait and see thing. Obviously this isn’t even coming from a statement from Google, so it’s not on the Google blog, it’s from another news outlet that’s reporting on something that Google is saying that they’re going to unveil in a month, so what it is and what the details are and how it plays out are really yet to be seen, so I guess we’ll have to wait and see.

路易斯：是的，所以我想这有点让人拭目以待。显然，这甚至不是来自Google的声明，因此它不在Google博客上，而是从另一个新闻媒体报道的，Google表示他们将在一个月内揭开面纱。到底有什么细节以及如何发挥作用还真是未知数，所以我想我们必须拭目以待。

Stephan: Yeah, I mean they probably came about this at some bar, they found some device that had —

斯蒂芬：是的，我的意思是他们可能是在某个酒吧里碰到的，他们找到了一些具有-

Patrick: They found Dart, someone at Google had left Dart laying on the bar next to an iPhone7 and they found both and this was a news worthy one.

帕特里克(Patrick)：他们找到了Dart，Google的某人已经将Dart放在iPhone7旁边的吧台上，他们发现了这两者，这是值得一提的新闻。

Stephan: This was the news worthy one, exactly.

史蒂芬：确切地说，这是值得一提的新闻。

Louis: Yep. So, another story I wanted to link to this week, and this is something I saw floating again across my Twitter stream, a bunch of people linked to, is an article on Smashing Magazine by, and I’m going to get the name wrong again, I always get people’s names wrong, but he’ll have to forgive me for this one, Lea Verou, I’m going to go with that —

路易斯：是的 。因此，我想链接到本周的另一个故事，这是我再次在Twitter流中看到的一堆东西，很多人都链接到了，这是Smashing Magazine上的一篇文章，而我将这个名字弄错了再说一次，我总是弄错人们的名字，但他必须为此原谅我，李·维鲁，我要同意—

Patrick: Sounds good.

帕特里克：听起来不错。

Louis: — as the pronunciation of that name, which is titled Help the Community Report Browser Bugs. So what it is, is this really in depth article sort of outlining the process of if you stumble across something that you think is a browser implementation bug how to isolate it, how to create a test case, how to report it on the browser’s bug tracker, test it in the latest nightly build of that browser, find out if it’s already been reported, so all of this stuff to really help browsers move along faster in their implementation of new and emerging standards like, for example, HTML5 and CSS3. So, I guess this is interesting because, how can I say this, we had IE6 which had a bunch of bugs that were known and the best you could do was come up with workarounds, so you’d blog about the workarounds that you had, and then after that we were kind of in this period of stagnation for a long time, but now suddenly you’ve got new standards and new browser versions being released really quickly, and what that leads to is you discover some interesting bugs sort of at the frontier of development, right, as new features are added and new specs are started to be implemented, and especially when the specs are worded perhaps ambiguously and there’s multiple different ways of interpreting it; it happens pretty frequently that if you’re playing with cutting edge stuff you’ll stumble across bugs and implementations. A lot of people maybe don’t have the experience or the knowhow to go out and sort of pare down your project to isolate the bug and then reproduce it and submit it so that the progress can go faster.

路易：该名称的发音，标题为“帮助社区报告浏览器错误”。那么，这实际上是一篇深度文章，概述了以下过程：如果您偶然发现了一些您认为是浏览器实现错误的东西，如何隔离它，如何创建测试用例，如何在浏览器的错误中报告它跟踪器，在该浏览器的最新夜间版本中对其进行测试，找出是否已报告，因此所有这些内容都可以真正帮助浏览器更快地实施HTML5和CSS3等新兴标准。所以，我想这很有趣，因为，我怎么说呢，我们有很多已知的IE6错误，而您可以做的最好的事情就是找到解决方法，所以您会在博客上介绍解决方法, and then after that we were kind of in this period of stagnation for a long time, but now suddenly you've got new standards and new browser versions being released really quickly, and what that leads to is you discover some interesting bugs sort of at the frontier of development, right, as new features are added and new specs are started to be implemented, and especially when the specs are worded perhaps ambiguously and there's multiple different ways of interpreting it; it happens pretty frequently that if you're playing with cutting edge stuff you'll stumble across bugs and implementations. A lot of people maybe don't have the experience or the knowhow to go out and sort of pare down your project to isolate the bug and then reproduce it and submit it so that the progress can go faster.

Patrick: I used up my joke for this story pre-show, so I will just say that everything you’ve said sounded great until you lost credibility when you said IE6 had bugs.

Patrick: I used up my joke for this story pre-show, so I will just say that everything you've said sounded great until you lost credibility when you said IE6 had bugs.

Louis: (Laughs)

路易斯：(笑)

Patrick: Right there is where I fell asleep.

Brad: Those aren’t bugs those are features.

Brad: Those aren't bugs those are features.

Patrick: (Laughs) No, this is a good tutorial and especially for someone, well, I don’t want to say someone like me because that’s an insult to other people (laughter). It would be someone more technically savvy than me who would be discovering bugs, but this is a good guide for reporting the bugs not just for browsers but also kind of a general good idea thing for technology software related bugs in general, how you go about finding a bug, making sure that it’s actually a problem, spending the time to read through the documentation and then, and only then, making the final step to actually report the bug to the proper party, so this is a really interesting article.

Patrick: (Laughs) No, this is a good tutorial and especially for someone, well, I don't want to say someone like me because that's an insult to other people (laughter). It would be someone more technically savvy than me who would be discovering bugs, but this is a good guide for reporting the bugs not just for browsers but also kind of a general good idea thing for technology software related bugs in general, how you go about finding a bug, making sure that it's actually a problem, spending the time to read through the documentation and then, and only then, making the final step to actually report the bug to the proper party, so this is a really interesting article.

Stephan: For me reporting web browser bugs is kind of like reporting spam on Twitter, I don’t feel like it does any good.

Stephan: For me reporting web browser bugs is kind of like reporting spam on Twitter, I don't feel like it does any good.

Patrick: So you don’t contribute to the solution, Stephan, you just stand by on the sideline and complain while the rest of us help make the world a better place.

Patrick: So you don't contribute to the solution, Stephan, you just stand by on the sideline and complain while the rest of us help make the world a better place.

Stephan: Well, my day-to-day life involves reporting bugs, so I don’t feel like doing it when I’m browsing the Web.

Stephan: Well, my day-to-day life involves reporting bugs, so I don't feel like doing it when I'm browsing the Web.

Brad: Stephan’s idea of reporting a bug is clicking that button “your browser crashed, would you like to report it,” sure (laughter).

Brad: Stephan's idea of reporting a bug is clicking that button “your browser crashed, would you like to report it,” sure (laughter).

Patrick: Would you like to notify Microsoft, yes.

Stephan: Yes, I would.

Brad: I gave back. I thought this article was great, I mean it’s definitely in depth and extremely detailed, but like you said it’s a good tutorial for anyone wanting to learn. But this actually reminded me quite a bit of, and they’re very similar, is pretty much the same approach you would take to like contributing to an open source application, I mean this is very, very similar; obviously browsers and web apps are a little different in how they’re built, but as far as the steps to take to determine if it’s a bug, to try to reproduce it, to search if it’s already been reported, I mean all that stuff is exactly the same. And I will say if you do actually go through this process whether it’s with open source or browser or anything for that matter, if you do discover something and actually are involved in helping fix it there’s a really good feeling behind that when it actually happens and you can say I found a bug in my favorite browser, I submitted it, they confirmed it, you know, fixed it because of me. Or an open source app, they took my code and used it because I figured it out, there’s a really good feeling behind that, so I definitely urge everyone to give it a shot sometime.

Brad: I gave back. I thought this article was great, I mean it's definitely in depth and extremely detailed, but like you said it's a good tutorial for anyone wanting to learn. But this actually reminded me quite a bit of, and they're very similar, is pretty much the same approach you would take to like contributing to an open source application, I mean this is very, very similar; obviously browsers and web apps are a little different in how they're built, but as far as the steps to take to determine if it's a bug, to try to reproduce it, to search if it's already been reported, I mean all that stuff is exactly the same. And I will say if you do actually go through this process whether it's with open source or browser or anything for that matter, if you do discover something and actually are involved in helping fix it there's a really good feeling behind that when it actually happens and you can say I found a bug in my favorite browser, I submitted it, they confirmed it, you know, fixed it because of me. Or an open source app, they took my code and used it because I figured it out, there's a really good feeling behind that, so I definitely urge everyone to give it a shot sometime.

Louis: Yeah, absolutely. And the other thing is even if you go out there and find — so you reduce it down, you discover that it’s actually a bug, you go out to the bug tracker on wherever, whichever browser maker or site you want to see, and find out that the bug has already been submitted, you can just subscribe to that ticket and then once its fixed in the nightly builds you’re made aware of it, and that gives you a better idea of where the state of development in your browser is, right; you get to know what’s going on and what the status is. If you found something that sort of prevents you from using a given technology on your website because, for example, there used to be this bug in WebKit browsers, so Chrome and Safari, where if you used a drop shadow that had a large blur it would make the scrolling really, really choppy like there was something really inefficient in there, so if you had a big blurry drop shadow it would be really, really sluggish, and basically that meant that you couldn’t use that in your sites because anyone coming to your site with Chrome or Safari would just have this awful experience, so you just had to turn it off. So knowing when that goes away, okay, now it’s been fixed in the nightlies so the next release of Chrome and Safari so give it about three or four months the problem goes away I know that I can use it, so staying in touch with the development of the browser is another big upside of this.

路易斯：是的，绝对。 And the other thing is even if you go out there and find — so you reduce it down, you discover that it's actually a bug, you go out to the bug tracker on wherever, whichever browser maker or site you want to see, and find out that the bug has already been submitted, you can just subscribe to that ticket and then once its fixed in the nightly builds you're made aware of it, and that gives you a better idea of where the state of development in your browser is, right; you get to know what's going on and what the status is. If you found something that sort of prevents you from using a given technology on your website because, for example, there used to be this bug in WebKit browsers, so Chrome and Safari, where if you used a drop shadow that had a large blur it would make the scrolling really, really choppy like there was something really inefficient in there, so if you had a big blurry drop shadow it would be really, really sluggish, and basically that meant that you couldn't use that in your sites because anyone coming to your site with Chrome or Safari would just have this awful experience, so you just had to turn it off. So knowing when that goes away, okay, now it's been fixed in the nightlies so the next release of Chrome and Safari so give it about three or four months the problem goes away I know that I can use it, so staying in touch with the development of the browser is another big upside of this.

Brad: A little trivia, do you guys happen to know what holiday it is today, today being September 13th the day we are recording this podcast, not the day the listeners are getting it.

Louis: Yeah, September 13th —

Brad: I hear Patrick Googling.

Patrick: National Peanut Day!

Louis: It’s close to Talk like a Pirate Day but I don’t think it is yet.

Louis: It's close to Talk like a Pirate Day but I don't think it is yet.

Patrick: We’re Googling pulling up random holidays (laughs). I see Defy Superstition Day on here when I Googled September 13th holiday.

Patrick: We're Googling pulling up random holidays (laughs). I see Defy Superstition Day on here when I Googled September 13th holiday.

Stephan: No, it’s International Chocolate Day.

Stephan: No, it's International Chocolate Day.

Louis: Yeah, Talk like a Pirate Day is September 19th, so next week will be Talk like a Pirate Day.

Brad: These are all good days, unfortunately none of these have anything to do with web development and design, but my day does and today is actually Programmer’s Day, it’s celebrated all around the world (laughter).

Brad: These are all good days, unfortunately none of these have anything to do with web development and design, but my day does and today is actually Programmer's Day, it's celebrated all around the world (laughter).

Patrick: All around the world; are you overdoing it a little bit celebrating all around the world.

Brad: All around the world. Hey, Wiki tells me it’s all around the world so it is. It’s actually celebrated on the 256th day of the year because that is the — because the number of distinct values that can be represented with and eight-bit byte, so there’s a little trivia for you, and that day is today September 13th, so happy Programmer’s Day.

Brad: All around the world. Hey, Wiki tells me it's all around the world so it is. It's actually celebrated on the 256th day of the year because that is the — because the number of distinct values that can be represented with and eight-bit byte, so there's a little trivia for you, and that day is today September 13th, so happy Programmer's Day.

Louis: So in a Leap Year it’s September 12th apparently, that’s really interesting.

Louis: So in a Leap Year it's September 12th apparently, that's really interesting.

Stephan: But wait I want to know when is a byte not eight-bits?

Louis: Never. I’m pretty sure the answer to that question is never.

Louis: Never. I'm pretty sure the answer to that question is never.

Stephan: It’s kind of redundant, right? Okay, nevermind.

Stephan: It's kind of redundant, right? Okay, nevermind.

Patrick: Happy Programmer Day Stephan, Brad and Louis.

Brad: So if you’re a programmer go out there, maybe somebody will buy you a beer, and if you are not a programmer maybe you should buy a programmer a beer, so I wanted to mention that. That actually wasn’t my spotlight; I just wanted to throw that out there.

Brad: So if you're a programmer go out there, maybe somebody will buy you a beer, and if you are not a programmer maybe you should buy a programmer a beer, so I wanted to mention that. That actually wasn't my spotlight; I just wanted to throw that out there.

Patrick: Either way Brad is suggesting you drink! No matter what just buy a beer, it doesn’t matter what day it is.

Patrick: Either way Brad is suggesting you drink! No matter what just buy a beer, it doesn't matter what day it is.

Brad: Yeah, just find me I’ll allow it, so I certainly won’t turn it down. My real spotlight is actually called the Evolution of Web.

Brad: Yeah, just find me I'll allow it, so I certainly won't turn it down. My real spotlight is actually called the Evolution of Web.

Patrick: Double dipping.

Brad: Yeah, I am a little bit. It was released by the Google Chrome team, and I got to be honest, I don’t know, it seems like this came out in the last few weeks, I could be completely wrong, it could’ve been out for a while, but it’s the first time I’ve seen it and it’s really, really cool so I wanted to make sure I shared it. But you can find it at evolutionofweb.appspot.com, and it’s actually this interactive timeline that shows exactly what you would think, the evolution of web by the most popular web standards and browser technologies, and it starts back in 1990 with the http protocol, you know going into HTML 1.0 and then it dives right into the first major browser, Mosaic version one, which was released in ’93, and actually it’s really neat because you kind of see the lifeline of all the various browsers, the ones that lasted, the ones that didn’t, and web standards and technologies as well.

Brad: Yeah, I am a little bit. It was released by the Google Chrome team, and I got to be honest, I don't know, it seems like this came out in the last few weeks, I could be completely wrong, it could've been out for a while, but it's the first time I've seen it and it's really, really cool so I wanted to make sure I shared it. But you can find it at evolutionofweb.appspot.com , and it's actually this interactive timeline that shows exactly what you would think, the evolution of web by the most popular web standards and browser technologies, and it starts back in 1990 with the http protocol, you know going into HTML 1.0 and then it dives right into the first major browser, Mosaic version one, which was released in '93, and actually it's really neat because you kind of see the lifeline of all the various browsers, the ones that lasted, the ones that didn't, and web standards and technologies as well.

Patrick: Yeah, as you first load it it’s almost like a horse race, go Netscape, go!

Patrick: Yeah, as you first load it it's almost like a horse race, go Netscape, go!

Louis: (Laughs)

路易斯：(笑)

Patrick: You can do it! Oh, no, it died; it fell off (laughter).

Brad: I was gonna say it lasted so long, I bet if you polled all the developers and designers out there when did Netscape end or die —

Louis: Yeah, I would not have guessed that it was 2008.

Brad: I would not have guessed 2008. A new version came out in 2007, who knew? We probably talked about it.

Patrick: This actually makes me realize how early we were online, like we weren’t online that early because different forms of the Internet have existed for a while, but I got online in 1995 and it’s right there before Internet Explorer even.

Patrick: This actually makes me realize how early we were online, like we weren't online that early because different forms of the Internet have existed for a while, but I got online in 1995 and it's right there before Internet Explorer even.

Brad: This whole timeline kind of puts it in perspective how young the Web really is, I mean it seems like it’s been around forever really, but I mean 20 years it’s really not that long of time in the grand scheme of things, and it’s amazing how things have come and gone in that short amount of time, too, different types of standards and technologies were all the rage and then like two years later they’re gone and nobody supports them, so it’s kind of neat looking at it visually.

Brad: This whole timeline kind of puts it in perspective how young the Web really is, I mean it seems like it's been around forever really, but I mean 20 years it's really not that long of time in the grand scheme of things, and it's amazing how things have come and gone in that short amount of time, too, different types of standards and technologies were all the rage and then like two years later they're gone and nobody supports them, so it's kind of neat looking at it visually.

Louis: Yeah, I’m looking forward to seeing how this evolves over time, like for example the JavaScript line just stops and Dart starts up replacing it.

Louis: Yeah, I'm looking forward to seeing how this evolves over time, like for example the JavaScript line just stops and Dart starts up replacing it.

Stephan: I’m interested to see how gun happy Google Chrome is for the next three years.

Stephan: I'm interested to see how gun happy Google Chrome is for the next three years.

Patrick: Yeah, and this is from Google obviously because Google has two spots, the last two the big innovators Chrome and Chrome OS are each separate categories.

Brad: I love that you can click on any browser and actually scroll through screenshots of each version.

Patrick: That is slick.

Brad: IE 1, 2, 3, 4, all the different versions for every browser, it’s definitely a blast from the past looking at some old Netscape screenshots and Internet Explorer 3, things like that.

Brad: IE 1, 2, 3, 4, all the different versions for every browser, it's definitely a blast from the past looking at some old Netscape screenshots and Internet Explorer 3, things like that.

Stephan: It makes me miss old Firefox, like version 1 and 2 looking at the screenshots; I miss it (laughter).

Brad: Back when it was innocent.

Stephan: Yes, back when it was innocent and the Internet was full of tables.

Louis: Yeah, I remember that, that was terrible.

Patrick: My spotlight is Back4thefuture.com, I found this via Crispian Burkes who is an active member on the SitePoint forums, and Nike has teamed up with the Michael J. Fox Foundation for Parkinson’s Research to sell 1,500 pairs of the 2011 Nike Mag, i.e. the shoe from Back to the Future. They light up, there’s a button inside that turns them on and off, and you can buy them on eBay now at Nikemag.ebay.com, and they are selling for thousands of dollars, two to three, four thousand, maybe even more depending on your size. But, it’s going to charity and Sergey Brin from Google has vouched to match I think up to 50 million dollars in donations from the auction, and someone else as well, I forget his name, sorry other kind donator, but it is pretty neat I think and a pretty neat shoe, if I had some discretionary income to spend I might even buy a pair, but yeah, so if you’re a big Back to the Future fan this is your opportunity.

Patrick: My spotlight is Back4thefuture.com , I found this via Crispian Burkes who is an active member on the SitePoint forums, and Nike has teamed up with the Michael J. Fox Foundation for Parkinson's Research to sell 1,500 pairs of the 2011 Nike Mag, ie the shoe from Back to the Future. They light up, there's a button inside that turns them on and off, and you can buy them on eBay now at Nikemag.ebay.com , and they are selling for thousands of dollars, two to three, four thousand, maybe even more depending on your size. But, it's going to charity and Sergey Brin from Google has vouched to match I think up to 50 million dollars in donations from the auction, and someone else as well, I forget his name, sorry other kind donator, but it is pretty neat I think and a pretty neat shoe, if I had some discretionary income to spend I might even buy a pair, but yeah, so if you're a big Back to the Future fan this is your opportunity.

Louis: My spotlight this week is something called Fitvids.js which is something put out by Think Vitamin this week, it’s this little JavaScript snippet, the purpose of which is to allow you to embed videos in a responsive site in a way that the actual video will scale along, so if you embed a YouTube video or a Vimeo video in an iFrame inside your website there are problems with putting that in sort of a fluid width container, so it will either break out of the container and cause some horizontal scroll bars or if you do resize it by sending a width on it in your CSS then you get something where the aspect ratio is all wrong. So, while we’ve had techniques for adjusting layout and adjusting images with responsive design and responsive sites, we haven’t really had anything to do a good job with video embeds which are a pretty key part of a lot of content based sites, and this is a great little JavaScript snippet and there are some cool demos if you want to have a look at it, and there’s a video demonstrating the functionality as well, so that’s mine.

Louis: My spotlight this week is something called Fitvids.js which is something put out by Think Vitamin this week, it's this little JavaScript snippet, the purpose of which is to allow you to embed videos in a responsive site in a way that the actual video will scale along, so if you embed a YouTube video or a Vimeo video in an iFrame inside your website there are problems with putting that in sort of a fluid width container, so it will either break out of the container and cause some horizontal scroll bars or if you do resize it by sending a width on it in your CSS then you get something where the aspect ratio is all wrong. So, while we've had techniques for adjusting layout and adjusting images with responsive design and responsive sites, we haven't really had anything to do a good job with video embeds which are a pretty key part of a lot of content based sites, and this is a great little JavaScript snippet and there are some cool demos if you want to have a look at it, and there's a video demonstrating the functionality as well, so that's mine.

Stephan: And I’ll go last I guess, after the phone call, mine is an article in the New York Magazine that’s called Bubble Boys and it’s kind of about all these geeks and programmers and hackers staying up late writing code in their dorm room being the future Steve Jobs and Mark Zuckerbergs, and it’s a really — it’s an interesting article about some of these guys and their obsession with code, so I figure some of our listeners will probably want to read that.

Stephan: And I'll go last I guess, after the phone call, mine is an article in the New York Magazine that's called Bubble Boys and it's kind of about all these geeks and programmers and hackers staying up late writing code in their dorm room being the future Steve Jobs and Mark Zuckerbergs, and it's a really — it's an interesting article about some of these guys and their obsession with code, so I figure some of our listeners will probably want to read that.

Patrick: Do we know any of these guys?

Stephan: I didn’t recognize any of the names.

Stephan: I didn't recognize any of the names.

Patrick: We’re the past generation at this point.

Patrick: We're the past generation at this point.

Louis: It’s very suited for Programmer’s Day.

Louis: It's very suited for Programmer's Day.

Patrick: A made-up holiday that I learned about five minutes ago.

Stephan: Maybe that’s why they came out with it today, I don’t know.

Stephan: Maybe that's why they came out with it today, I don't know.

Patrick: Probably not. I don’t think New York Magazine makes publishing decisions based upon made-up holidays.

Patrick: Probably not. I don't think New York Magazine makes publishing decisions based upon made-up holidays.

Brad: Any title that says How Coding is like Cocaine is definitely geared towards developers.

Stephan: (Laughs) Oh, I totally missed the subtitle there.

Louis: Alright, well that’s as good a cue as any to wrap this one up.

Louis: Alright, well that's as good a cue as any to wrap this one up.

Brad: I’m Brad Williams from Webdev Studios and you can find me on Twitter @williamsba.

Brad: I'm Brad Williams from Webdev Studios and you can find me on Twitter @williamsba .

Patrick: I’m Patrick O’Keefe for the iFroggy Network, I blog at managingcommunities.com, on Twitter @ifroggy, i-f-r-o-g-g-y.

Patrick: I'm Patrick O'Keefe for the iFroggy Network, I blog at managingcommunities.com , on Twitter @ifroggy , ifroggy.

Stephan: I’m Stephan Segraves; my blog is Badice.com and I occasionally Tweet @ssegraves.

Stephan: I'm Stephan Segraves; my blog is Badice.com and I occasionally Tweet @ssegraves .

Patrick: You also occasionally blog (laughter).

Louis: And you can follow SitePoint on Twitter @sitepointdotcom, that’s SitePoint d-o-t-c-o-m, and you can follow me on Twitter @rssaddict. If you go to sitepoint.com/podcast that’s a place to subscribe to the show, to find all our previous episodes, to leave a comment on this show, anything you want to do related to the podcast is found at sitepoint.com/podcast. Alright, thanks everyone, see you next week.

Louis: And you can follow SitePoint on Twitter @sitepointdotcom , that's SitePoint dotcom, and you can follow me on Twitter @rssaddict . If you go to sitepoint.com/podcast that's a place to subscribe to the show, to find all our previous episodes, to leave a comment on this show, anything you want to do related to the podcast is found at sitepoint.com/podcast. Alright, thanks everyone, see you next week.

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/sitepoint-podcast-130-high-on-responsive-design/