The genius behind Google’s web browser

崇拜,真正的世外高人(⊙o⊙)哦 ( ps:为什么国外高手都用Mac )


书中漫画地址:看这里@google     或者 本帖后附件下载 ( 用firefox打开 )

 


原文链接:The genius behind Google’s web browser
作者:Rob Minto
译者:Esther
校对:pestwave

 

 

     




奥尔胡斯(Aarhus)是丹麦第二大城市,也是日德兰半岛(Jutland)的非正式首府。在该市郊外5英里的地方,有一座改造过的农舍。里面有宽敞的木地板和拱形的顶(曾经是马厩的一部分),在距离DVD播放机不远的地方摆着一个大的棕色皮沙发。从外面看,这座房子看上去仍略显陈旧:粗糙的石子路,凹陷得小窗;但正是这里孕育了互联网未来的关键部分之一。

从哥本哈根开车到这里的路程比预期的更漫长,房子也很难找。房子的主人叫拉斯•巴克,是一个年轻的编程天才,他之所以把家安在这里是因为他非常不愿意让别人找到自己。他的阿尔萨斯牧羊犬,米奇,见到我们也有些受惊:主人把它看住之后我才敢下车。

那是丹麦寒冷十二月的一天。这地方比爱丁堡还靠北,但天色如同东英格兰沼泽地的一样,灰蒙蒙一片。我们握手的时候,巴克看上去很不自在,我觉得他好像压根不想让我靠近他的居所。不过,我们还是走进了放有棕色皮沙发的拱形顶房子里。现在这里是家庭影院,之前曾是他编程的办公室。温度只比外面稍高一点。我拿出笔记本的时候还在瑟瑟发抖。“好吧,您想了解些什么呢?”巴克发问了。我们有四个小时的采访时间。

拉斯•巴克并非家喻户晓的名字——至少这个拉斯•巴克不是。在丹麦还有一个拉斯•巴克更出名,那是一位职业自行车选手。但是这位巴克可比任何运动员对你生活的影响更加深远。他最近的计算机软件程序V8是Chrome浏览器(谷歌商业计划的关键)的一部分。

网页浏览器都不赚钱,无论是IE、Safari、还是火狐。那么,新浏览器对谷歌的重要性何在?为什么要投入时间和精力在免费产品上,而这些又不能给公司带来收入?答案不在浏览器本身,而在于它能访问的内容:也就是网络应用程序。这些才是给谷歌带来收入的东西。比如,该公司对Google文档寄予厚望,这是一套在线办公软件,和微软的当代企业工具桌面版Office程序(Word, Excel和PowerPoint)类似。但为了更好地体验获得这些程序和其他在线应用,用户需要更好的浏览器,以便更好地运行相关代码。我们很多人已经在使用网络程序了,比如Hotmail, Yahoo邮箱或Gmail,不过它们都相对简单,比起一般的桌面软件,它们的复杂性相形见绌。

浏览器已经无法处理日益复杂的网络应用。就好比是很多高性能的跑车跑在辙颠簸不平的路上一样。但是没有哪家跑车制造商会出钱修路,毕竟自己修路对手也会沾光,更不要提高昂的费用。软件开发的成本不高,但依然存在竞争问题。不过谷歌说它不在乎,它说:没有好的浏览器,大家伙儿都会遭殃。

通过网络访问复杂程序的能力被称为“云计算”,并且谷歌并非唯一一家声称领先的公司。即使微软,桌面应用软件和操作系统的代名词,也在跃跃欲试。史蒂夫•鲍尔默,微软的首席执行官,已经承诺研发“在互联网中运行的操作系统”——他称之为“视窗云”,不过要想真正实现云计算,必须改进浏览器。

恰在此时,巴克出现了。这个丹麦人首次在加州硅谷引起人们的注意是在1991年,那时他在Sun公司工作,后来成为业界最佳程序员之一。1994 年,他离开Sun,帮助创建了Animorphic系统,该公司后来被Sun收购。再次回到Sun之后,巴克开发了后来成为Java HotSpot(行业标准计算系统之一)的程序。

可是2000年初,他却离开了计算机世界的核心,回到了丹麦,搬家是为了幸福生活,为了他的女儿们(他想让她们上丹麦语学校),为了自己的身心健康。美国的开发者社区工作很紧张,生活方式不健康。当巴克回到丹麦时,两个月之内他减了20斤(多亏了美国的阿式饮食疗法【Atkins diet】),而且再也没有反弹。

2002年,巴克在奥尔胡斯创建了一家名为OOVM的公司。2004年,他将公司卖给了一家瑞士公司Esmertec,然后又在该公司干了两年,帮助两个公司的融合。离开Esmertec时,他并不特别想找新项目:他有足够的钱养家糊口,也有各种打发时间的方式,包括粉刷农舍的计划。他估计得要一年时间。

然后Google的电话就来了。对于Google,巴克是不二选择——他编写了JavaScript引擎(Chrome的核心部分)。对于巴克,为 Google工作就是 “小菜一碟”。“我不在乎当什么高级经理。我在乎的是推动技术边界。”巴克接受了这份工作,但不会回到加州。事实上他从没打算再次回加州——虽然谷歌的人性化办公室闻名远近,餐厅里的美食,还可以免费理发,巴克却宁可在家工作——离总部5000英里,相差9个时区。谷歌做好了“信任我的准备。他们知道我不会消磨时间。”重新装修农场的计划要搁置一下。“最后,”他说,“我只有14天的时间(粉刷)。涂料还留着呢。”
巴克在日德兰半岛的居家办公室,他和妻子,孩子还有宠物阿尔萨斯牧羊犬米奇住在一起

巴克在日德兰半岛的居家办公室,他和妻子,孩子还有宠物阿尔萨斯牧羊犬米奇住在一起

巴克开始工作,在现在是家庭影院的地方建立了办公室。农舍是围绕院子修的,家就在办公室对面。每天,他走过石子路到办公室,然后开始写代码。每天结束时,他又穿过院子,走回家,把工作彻底放下。在这些行走之间,他投入到浏览器开发中,有了这种浏览器,其他人就有更多机会做他所做的事:在家工作,与总部连接,所需要的全部工具就是互联网的力量。

巴克也许是个计算天才,但他是上大学之后才开始接触计算机的。“高中的计算机室又黑又臭,只有书呆子才去,”他说,“我喜欢运动。弹板跳水–特酷。我后来才成为书呆子的。”

在《局外人》中,Malcolm Gladwell探讨了天才和成功的本源,作者陈述了这样的观点,你需要苦练10000小时才能在所选择的领域里真正成功。我问巴克,你做足10000小时了么?我能看出来他觉得这压根不相关;他对此也不感兴趣。“我只是很高兴大器晚成”,他再次强调,“而不是年少就成名。”

也许是因为大器晚成,巴克从不热衷于传说中那种靠咖啡提神彻夜写编程代码的故事。不过这可能也缘于巴克精通的程序类型:“虚拟机”,这是计算机科学家Gerald Popek 和他的项目伙伴Robert Goldberg早在1970年代所探讨的一个想法。虚拟机器名副其实——真正机器的计算机世界版,能够在单机程序或整套程序上使用。Chrome浏览器属于后者。V8,巴克的虚拟机器,编辑不同程序通用的代码,以便减少冗余,让网络应用程序更快运行。

“虚拟机是头怪兽,”Bak说,“没有完美的解决方案,你只能为“最佳时机”进行优化。有很多技术含量在其中。这是个漫长的游戏,你玩不完的。

“工作量是恒定的,”他补充说,“所以我总要停下来吃饭。你可以有正常生活。”对巴克而言,这意味这家庭和隐私。工作/生活平衡的问题在谈话中一再冒出来——虽然他不反对美式生活,但显然他更喜欢丹麦的生活方式。“在美国,需要进取和格外自信。欧洲的生活方式则不然。而在美国,你能有晋升机会,能与技术发展保持同步。在欧洲,你就只能做办公室当经理,没有活可干。”通过在丹麦为谷歌工作,巴克意在一箭双雕,同时享受两个世界中最好的东西。

巴克将他的V8项目成为笑话:V8引擎就好像汽车镀铬发动机罩下面安装的那个东西 ——“而Google就那么酷——不论项目最初的名字是什么,以后不会改变。不会因适应市场营销而改变名字。”

从开展谷歌项目的第一天,巴克就征募了他以前的学生卡斯帕•伦德的帮助。伦德年轻也更外向,他同意来农舍上班。他还有其他作用——让巴克娱乐。伦德和他那竞争力很强的老板习惯于用乒乓和Wii网球来调剂工作。谁的乒乓能赢,我在想;巴克回答说:“问卡斯帕。”哦,那么卡斯帕能赢喽。“不是。”稍后,他透了口风:“他打得比我好,不过还是我赢。”他们的关系已经从师生变得更像同事,但又不完全是;有朋友把这比作巫师和学徒。

许多程序都是用以前的版本或相关代码创建的,但V8是白手起家——一片空白。后来当我在丹麦之旅中遇见伦德时,他很乐于强调这一点:“这是最纯粹的编码形式。”巴克显然有共识——在伦德说话的时候,他不停地微笑。

随着V8深入,项目扩展,巴克和伦德把编写代码从农舍搬到奥尔胡斯的一座大学,巴克在此任教。骑车需要30分钟,把通勤当作锻炼和巴克将工作和生活平衡的哲学不谋而合。

大学办公室虽然在距离上与加州山景Googleplex总部遥遥相隔,不过一看就是谷歌的风格。在进门的地方,五颜六色的椅子和小布袋到处都是,然后是两个主要房间,有10来个人在这里工作。不过没有餐厅,只有厨房,里面有坚果贩卖机,还有一冰箱的瓶装水和健怡可乐。巴克引入了无糖政策:“不是完全无糖——你可以从水果里得到自然糖分。不过没有巧克力,没有明目张胆的糖果而已。”

每个人愿意接受这里的管理制度,见证了办公室的忠诚度。好像所有人都骑自行车来上班,下午5点左右就离开。“我们开始的也早,累了还工作没有意义,所以我们就回家,”伦德说。这是两小时前巴克在他的农场上给我讲述的工作生涯的逐字描述。这令人心服口服。但和谷歌的人沟通怎么办?当巴克、伦德和其他成员在奥尔胡斯时间下午5点下班时,旧金山还不过早上9九点。他们是利用硅谷24小时工作的趋势吗,还是并不需要和总部保持联络?伦德说大多数时候用电子邮件就可以了。我采访的当天,在其他同事下班之后,巴克需要参加电话会议。他努力不把情绪流露出来,但很显然,他并不想参加。

编程可以是很单调的事情。虽然巴克和伦德紧密合作,但还是有种遗世独立的感觉。你写代码,测试,修改,再写,周而复始,直到你得到自己需要的。对于巴克,这很简单,也很隐蔽。然后,出于某种原因,外界就想进来干扰——想要认识你,想要了解你的工作。

巴克很看重自己的隐私。在家给他照相也让他明显不自在。但当我告诉他,把他的名字输入谷歌搜索引擎里,得到的都是一页又一页和他同名的自行车手,这肯定遮挡了他本该有的光彩,他耸耸肩,“我老了,不在乎别人说我什么。”

真正让他恼火的是大家误会他的工作——或按他的说法,“技术”。他举了一个例子,在有篇关于他的文章里,记者混淆了Java和 JavaScript(前者是可以在线进入的独立程序,而后者是依靠浏览器的脚本语言)。对此我们都笑起来,在那么一瞬间,我觉得巴克和我有了默契。

世界以非同寻常的方式发现了Chrome。故事是通过谷歌早前发布的专门漫画传出去的——显然犯了个错误。公关忙成一团来支持这个消息,匆匆忙忙地举行了电话会议,发表博客日志解释到底发生了什么,随后又是新闻发布会,然后在Googleplex举办产品展示。

在群情激动地讨论为什么谷歌要发布新浏览器,泄密是不是有意而为之时,认真看漫画的人寥寥无几。虽然是由Scott McCloud(也算是漫画界的传奇人物)编撰的漫画,这可是艰难的工作。讨论的是Java Script (不是Java哟!),CPU和存储器漏洞——大多数都不想知道的计算细节。但是这漫画却显示了Chrome特性背后的思想理念,还有独立小组解决拼图各个部分的方式。巴克和伦德最初出现在第二页上,不过是到了大约三分之一的时候,在第13页,才有对“丹麦V8团队”的介绍,解释了这个“虚拟机器”的开发,不过没有提到为什么V8距离谷歌总部那么远,隔着大陆和海洋。

伦德和巴克喜欢这个漫画。在奥尔胡斯办公室里,整幅漫画都用相框框起,挂在墙上。“开始,我觉得这想法很怪异,”巴克说。“但是我意识到这太有才了。与其他白皮书相比,这要强10倍。大家都觉得这很有趣。”

我怀疑他们俩都喜欢它的原因是它平等地对待巴克和伦德——虽然与巴克相比,伦德可算是个大块头。“让我看上去像个15岁的男孩,”巴克说。他矜持地微笑了。

在刚推出的100天内,Chrome就已经吸引了一千万用户。虽然这个数字很震撼,可也只代表在线浏览器使用的百分之一。它还需要假以时日方能与火狐、IE及其他产品抗衡。去年12月,谷歌宣布Chrome已经结束研发或Beta(测试)阶段,准备在某些个人电脑上作为预选安装的浏览器发行。这样可以迅速增加用户数量。而且,欧洲委员会与微软就其IE浏览器如何并入视窗(Windows)操作系统所产生的反托拉斯战争以及其他纷争可能会给谷歌这样的竞争者占领市场的机会。

抛开法律和市场份额不说,技术挑战已经存在了。“微软不得不创建比V8更好的东西,”巴克说。很多技术观察家很怀疑他们能够在短时间内完成:在测试中,V8处理JavaScript的速度比最常见的IE浏览器要快56倍。“我们一开始就是高标准,”巴克说。随后谦虚地加了一句:“还算成功啦。”

即使Chrome漫画没有让巴克迅速成名,他的知名度在这几个月中也迅速增加。越来越多的人想了解Chrome背后的这个人。他宁可写虚拟机器,也不愿意管理奥尔胡斯办公室,而且他宁可做其他所有事情,而不是和记者谈话,可那是游戏的一部分,他接受了。话虽如此,他离Facebook的创建者马克• 扎克伯格或比尔•盖兹还有很远的距离。我问,在漫画出来之后,你有没有收到粉丝的邮件?他笑了:“没。不过我也没有收到抱怨的邮件。”

背景知识介绍:浏览器大战

互联网在其短短历史中,已经看到各种浏览器的产生,但是主角只有四个:网景(Netscape)导航器,IE浏览器,火狐(Firefox)和Chrome。

说到普遍使用,网景浏览器是第一。每个人都用过导航器——部分原因是没有其他正儿八经的替代者——而且它用起来不错。然后是微软的IE浏览器,该产品是公司主导产品Windows操作系统的一部分,从而带动着它的增长。截止1998年,IE在使用方面已经取代了网景。

微软被指控违反了反托拉斯法,但那时已经太迟。IE控制了90%的市场份额,虽然有官司在身,时至今日,它还是以默认浏览器的身份安装在世界上绝大多数个人电脑上。网景被美国在线(AOL)收购了,在历经波折之后,于2007年停止研发。

要不是“开源”社区,事情到此就结束了。开源软件曾是(而且在某种程度上仍然是)微软之鞭。总裁史蒂夫•鲍尔默曾说Linux的开源操作系统是癌症。此类软件由软件开发者团队的人不断改善,他们这么做基本上是什么都不为。劳动果实通常都免费分发。1998年,网景将导航器的代码转换为名为 Mozilla的开源项目——火狐正是从此演变而来的。

火狐占了IE市场份额的20%,而且仍在增长。它的众多属性——如分页浏览和读取设置——在其他产品如浏览器Opera上出现得其实还更早,但是得益于口碑相传、出色的市场营销和火狐的对于技术水平较高用户的吸引力,它已然成了IE最强劲的挑战者。而且,它是开源的,第三方开发者可以通过创建新应用程序扩展火狐的容量,让它更加强大。

在2008年谷歌推出Chrome之前,浏览器市场好像成了IE和火狐二者之间的竞争,当然也得提及以Mac为基础的Safari。

Chrome仍然只有百分之一的浏览器份额,但这会增长。有了拉斯•巴克的V8引擎,Chrome简直如虎添翼。该浏览器使用许多开源代码和开放标准,但也引入了一些重要的创新,如独立页面的使用。这听起来很无聊,但其实很至关重要。原因如下:通常,通过浏览器运行几个网络应用程序会导致崩溃。而且当一个浏览器页面崩溃时,整个程序都需要重启,其他页面上的工作或活动都会丢失。

Chrome的运作方式意味着任何浏览器的崩溃都仅限于当页,所以,如果你在一个页面上写邮件,而另一页面的视频崩溃了,你的邮件并不受影响。你可以把崩溃的页面关掉,继续工作。让浏览器以这样的方式工作——好像桌面一样——对于未来网络应用程序至关重要。

当然,Chrome的运行速度也很关键。为了网络应用程序能够成功,它们需要反应迅速,否则用户会郁闷。速度、稳定、安全——这些都是我们未来在线活动的关键方面。而浏览器则是大门。




原文:


About five miles outside Aarhus in Denmark – the country’s second-­biggest city and the unofficial capital of Jutland – sits a converted farmhouse. Inside, in a large wood-floored space with vaulted ceilings – once part of the stables – a big brown leather sofa is positioned a few feet from a DVD player. From the outside, with its rough cobbles and small, recessed windows, the farmhouse still seems steeped in the past; yet this is the place where a key part of the future of the internet first took shape.

The drive from Copenhagen has taken longer than expected, and the farmhouse is hard to find. Lars Bak, its owner and a programming genius to his peers, made his home here for a reason – he doesn’t particularly want to be found. His ­Alsatian, Mickey, isn’t pleased to see us either: the dog has to be restrained before I even think about stepping out of the car.

It’s a cold December day in Denmark. We are further north than Edinburgh, but the sky is the uniform grey you see in the East Anglian fens. Bak seems uncomfortable as we shake hands, and I get the feeling that he wants me nowhere near the part of the farmhouse where he lives. Instead, we go into the vaulted room with the brown leather sofa. Nowadays it is a home cinema, but before that it was the office where Bak did his programming. The temperature is only slightly warmer than outside. I shiver as I take out my notebook. “So, what do you want to know?” Bak demands. We have four hours to go.

Lars Bak isn’t a household name – or at least this one isn’t. There’s a better-known Lars Bak in Denmark who’s a professional cyclist. But this Bak will have a more profound impact on your life than any sportsman. His most recent computer software program, called V8, is part of the Chrome web browser, a lynchpin in the business plan of Google.
EDITOR’S CHOICE
More from Reportage - Nov-24

Companies don’t really make money out of web ­browsers – the Explorers, Safaris and Firefoxes of the ­internet. So why is a new one so important to Google? Why invest time and effort in a free product that generates no income for the ­company behind it? The answer is not in the browser itself, but in the things it can access: namely, web-based software programs. These are a source of revenue for Google. The company has high hopes for Google Docs, for ­example, an online suite of programs that replicates many of the desktop ­programs in Microsoft’s Office – Word, Excel and PowerPoint – the tools of the modern business. But to deliver better ­versions of those programs and others over the internet, you need better ­browsers, ones that can handle the code that will be thrown at them. Many of us already use web-based ­programs: e-mail accounts such as Hotmail, Yahoo mail or Googlemail, for example. But they are relatively simple: their complexity pales in comparison with the programs stored on the average computer desktop.

The sophistication of web applications is increasing much faster than the corresponding power of the browsers. It’s like having lots of high-performance sports cars using rutted, bumpy roads. And yet no car manufacturer has ever invested in road building. That sort of move would, after all, benefit competitors equally, not to mention being massively expensive. Software development doesn’t cost as much but the ­competitor problem remains. But Google says it doesn’t mind: without an improvement in browser performance, the company argues, we all suffer.

The ability to access complex programs through the web is known as “cloud computing”, and Google isn’t the only one arguing that it’s the way ahead. Even Microsoft, the company synonymous with applications and operating systems located on the desktop, has talked about moving into “the cloud”. Steve Ballmer, Microsoft’s chief executive, has promised an “operating system that runs in the internet” – something he has dubbed “Windows Cloud”. But for cloud computing truly to take off, web browsers need to be better.

And that’s where Bak comes in. The Dane had first appeared on California’s Silicon Valley radars in 1991, when he joined Sun Microsystems and began building a reputation as one of the industry’s best programmers. He left to help start Animorphic Systems in 1994, which was then acquired by Sun. Once back at the company, Bak developed what would become Java HotSpot, an industry-standard computing system.

In early 2000, however, he left the hub of the computing world for Denmark, moving home for the quality of life, for his daughters, whom he wanted to attend Danish schools, and for his wellbeing – both mental and physical. The developer community in the US can be intense, the lifestyle unhealthy. When Bak returned to Denmark, he lost 20kg in two months (thanks to that very American phenomenon, the Atkins diet), and he hasn’t put it back on.

In 2002, Bak started a company, OOVM, which was based in Aarhus. In 2004, he sold it to a Swiss company, Esmertec, and stayed on for two years, helping integrate the two groups. When he left Esmertec, he wasn’t particularly looking for a new project: he had money to support ­himself and his family, and ways of keeping busy, including a plan to paint the farm. It would take a year, he reckoned.

Then came the call from Google. For Google, Bak was the obvious choice – he had the experience and talent to build the vital component for Chrome, its JavaScript engine. For Bak, working for Google was a “no-brainer”. “I don’t care about being a top-level manager. It’s about pushing the technological envelope.” Bak was ready for the work, but not for a return to California. In fact, that wasn’t even an option – despite Google’s notoriously worker-friendly offices, with gourmet food in the canteen and free haircuts on site. Instead, Bak would work from home – more than 5,000 miles and nine time zones from headquarters. Google was “prepared to trust me. They knew I wasn’t going to goof off.” The plan to redecorate the farm went on hold. “In the end,” he says, “I only had 14 days [for the painting]. I still have the paint.”

Bak at his home-turned-office on the Jutland peninsula, where he lives with his wife, children and pet Alsatian, Mickey
Bak started work, setting up an office in what is now the home cinema. The farmhouse is built around a courtyard, with the family home opposite the office. Every day, he walked across the cobbled stones to his office and started writing code. And at the end of each day, he walked back across the courtyard and left it all behind for the night. In between those strolls, he threw himself into building a browser that would increase the possibilities for others to do what he was engaged in: working from home, attached to the head office and all its tools only by the power of the internet.

Bak may be a computing genius, but he didn’t touch a computer until he was at university. “The computer room at high school was a dark and smelly place for nerds,” he says. “I played sport. Springboard diving – which is pretty cool, by the way. The nerdy stuff came late.”

In Outliers, Malcolm Gladwell’s 2008 exploration into the origins of talent and success, the author explores the idea that you need to practise for 10,000 hours to truly excel in your chosen field. Has Bak done his 10,000 hours, I ask? I can tell he thinks it’s irrelevant; he’s not interested. “I’m just glad I bloomed late,” he emphasises again, “rather than as a teen.”

Perhaps because of being a late-blooming nerd, Bak has never gone in for the caffeine-fuelled all-night coding sessions of programming legend. But that may also be due to the type of program Bak specialises in: the “virtual machine”, a concept originally explored in the 1970s by computer scientist Gerald Popek and his project partner Robert Goldberg. Virtual machines are what they sound like – computer-world versions of real machines, capable of running a single computer program or a whole range of programs. The Chrome browser falls into the latter category. V8, Bak’s virtual machine, compiles pieces of code common to different programs in order to cut down on duplication and allow web applications to run faster.

“Virtual machines are a strange beast,” says Bak. “There’s no perfect solution, instead you optimise for the ‘sweet spot’. There’s a lot of craftsmanship. It’s a long game, you can’t burn out.

“There’s a constant workload,” he adds, “so I always stop for dinner. You can have a normal life.” For Bak this means family and privacy. The issue of work/life balance crops up again and again in conversation – and though he’s not anti-American, he clearly prefers the Danish way of life. “In the US, there is an aggressiveness, the extra level of belief in yourself that is needed. The European way is less aggressive. But in the US, you can get promoted and stay in touch with the technical side. In Europe, you turn into a paper manager. It’s hard to get your fingers dirty.” By working in Denmark for Google, Bak was aiming for the best of both worlds.

Bak called his project V8 as a joke: the V8 engine is what you might find mounted underneath the chrome-finished bonnet of a car – “and Google is cool like that – whatever the project working name is, that’s what it’s called. There’s no intervention by marketing to give it some name.”

From day one on the Google project, Bak enlisted the help of one of his former students, Kasper Lund. Lund is a smaller, younger, more outgoing character, and he agreed to come to the farmhouse to work. He also served another function – keeping Bak entertained. Lund and his competitive boss got into the habit of interspersing work with battles of ping pong and Wii tennis. Who wins at the former, I wonder; Bak responds: “Ask Kasper.” Oh, so Kasper then? “No.” Later, he lets slip: “He’s a better player, but I win.” Their relationship has changed from teacher-student to something closer to peers, but not quite; a friend describes it as wizard and apprentice.

Many computer programs are built using previous versions, or related code, but V8 was started from scratch – a blank slate. When I meet Lund later in my Denmark trip, he takes great delight in underscoring this fact: “It’s the purest form of coding there is.” Bak clearly agrees – as Lund speaks, he can’t stop smiling.

As V8 grew and the project expanded, Bak and Lund moved from coding in the farmhouse to an office at the university in Aarhus where Bak teaches. It’s a 30-minute cycle ride away, and the commute-as-exercise fits nicely into Bak’s philosophy of balancing work and life.

    Battle of the browsers

    The internet has seen the creation of many browsers in the course of its short existence, but the main story has only four protagonists: Netscape Navigator, Internet Explorer, Firefox and Chrome.

    In terms of popular usage, Netscape Navigator was the first. Everyone used Navigator – in part because there weren’t any serious alternatives – and it worked fine. Then came Microsoft’s Internet Explorer (IE), which was integrated into the company’s dominant Windows operating system, driving its growth. By 1998, IE had overtaken Netscape in terms of usage.

    An antitrust suit was filed against Microsoft, but by then it was too late. IE controlled over 90 per cent market share and, despite the legal wrangling, to this day it is still shipped as the default browser on most of the world’s PCs. Netscape was bought by AOL, and after much dithering was taken out of development in 2007.

    The story would end there but for the “open-source” community. Open-source software was (and to an extent still is) the scourge of Microsoft. Chief executive Steve Ballmer once referred to the Linux open-source operating system as a “cancer”. Software like this is constantly improved by a community of software developers who work on the project for little or nothing. The fruits of their labour are usually distributed free. In 1998, Netscape turned the code of Navigator into an open-source project called Mozilla – and out of that grew Firefox.

    Firefox has taken 20 per cent of IE’s market share, and is still growing. Many of its features – such as tabbed browsing and accessibility settings – were available earlier on other products, such as the browser Opera, but thanks to word-of-mouth, good marketing and Firefox’s appeal to more technically literate users, it has grown to be IE’s biggest challenger. And because it is open-source, third-party developers can extend Firefox’s capabilities by building new applications, making it an even more powerful tool.

    The browser market was looking like a two-horse race between IE and Firefox, with an honourable mention for the Mac-based Safari, until Google launched Chrome in 2008.

    Chrome still has only about 1 per cent of the browser share but that will grow. With Lars Bak’s V8 engine, Chrome is incredibly quick. The browser uses a lot of open-source code and open standards, but has also introduced some important innovations, such as its use of independent tabs. This sounds dull, but it’s critical. Here’s why: normally, running several web-based applications through the browser can lead to a crash. And when one browser tab crashes, the whole program needs to be restarted, losing any work or activity going on in other tabs.

    Chrome runs in a way that means any browser crash is limited to just that tab, so that if you are composing an e-mail in one screen, and a video crashes in another, the e-mail you are writing is not affected. You can close the crashed tab and continue working. Making the browser operate in this way –like the desktop – is crucial for the future of web applications.

    Of course, the speed at which Chrome functions is also vital. For web-based applications to be a success, they need to respond quickly, or users will become frustrated. Speed, stability, security – these are all critical areas for the future of everything we do online. And the browser is the gateway.

The office at the university may be a long way from head office, the Mountain View Googleplex in California, but it is still recognisably Google. Colourful chairs and beanbags are scattered through the entrance area, which leads on to two main rooms where up to a dozen people work. But there’s no canteen, just a kitchen with a nut dispenser and a fridge full of bottled water and Diet Coke. Bak has introduced a no-sugar policy: “It’s not no sugar as such – you get natural sugar from fruit. But no chocolate, no obvious candy.”

It is testament to the loyalty in the office that everyone has signed up to this regime. Everyone seems to cycle, too, and to leave work around 5pm. “We start early, and when you get tired, there’s no point doing any more so we go home,” says Lund. It’s almost a word-for-word description of the working life that Bak described to me two hours earlier at his farm. And it’s convincing. But what about communication with the gang at Google? When Bak, Lund and crew leave the office at 5pm Aarhus time, it is still only 9am in San Francisco. Are they taking advantage of Silicon Valley’s tendency to work around the clock, or is it really not necessary to be in touch with headquarters? Lund says that overnight e-mailing works fine for most situations. The day of my visit, Bak is due to participate in a conference call after the rest of the office has gone home. He tries to play down his feelings about this, but it’s obvious he would rather not have to take part.

Programming can be a very solitary pursuit. Although Bak and Lund work in close collaboration, there is still a sense of isolation from the rest of the world. You write code, test it, refine it, write more, and just keep going until something works like you need it to. For Bak, it’s very simple, and very secluded. And then, for some reason, the rest of the world wants in – to know about you and your work.

Bak values his privacy. He is clearly uncomfortable having his photo taken at his home. But when I point out that typing his name into the Google search engine brings up page after page related to his cyclist namesake, and suggest that this must shield him from undue attention, he shrugs. “I’m too old to care about what people say about me.”

What does annoy him is people misunderstanding his work – or “the technology”, as he puts it. One example he gives is an article about him in which the journalist confuses Java and JavaScript (the former is a stand-alone program which can be accessed online, the latter is a browser-dependent scripting language). We both laugh at the mistake, and for a moment I feel like Bak and I have clicked.

The world found out about Chrome in an unusual way. The story broke via a specially commissioned comic that was sent out early by Google – apparently in error. There was a PR scramble to shore up the news, involving hastily arranged conference calls and a blog post explaining what had happened, followed by a press conference and demonstrations of the product at the Googleplex.

In the excitement and debate about why Google was releasing a new browser, and whether the leak was deliberate, few people really looked carefully at the comic. Despite being created by Scott McCloud (something of a legend in the world of comics), it’s tough going. There is talk of Java­Script (not Java!), CPU and memory leaks – details of computing that most people don’t want to know. But the comic does show the thinking behind many of the features of Chrome, and the way separate teams set about solving each part of the puzzle. Bak and Lund first appear briefly on page two, but it’s around a third of the way through, on page 13, that we are properly introduced to “The V8 team in Denmark”, who explain the development of this “Virtual Machine”. There’s no mention of why V8 was built a continent and an ocean from Google headquarters.

Lund and Bak like the comic. It’s framed in its entirety on the walls of the Aarhus office. “At first, I thought it was a strange idea,” says Bak. “But then I realised it’s brilliant. Compared to the usual white paper you get, it’s 10 times better. People thought it was funny.”

I suspect one reason they both like it is also that it treats Bak and Lund as equals – although Lund is characterised as physically hulking compared with Bak. “It made me look like a 15-year-old boy,” says Bak. He allows himself to smile.

Chrome attracted more than 10 million users in its first 100 days. Although that’s an impressive number, it still only translates into about 1 per cent of browser usage online. It will be a while before it can compete with Firefox, Internet Explorer and others. In December last year, Google announced that Chrome was now out of its development, or Beta, phase and is ready to be shipped as a pre-installed browser on some PCs. This could rapidly increase the number of users. Moreover, the European Commission’s antitrust battle with Microsoft over, among other things, how its own browser, Internet Explorer, is integrated into its Windows operating system may give competitors such as Google a chance to claim ground.

Legislation and market share aside, the technical challenge has been laid down. “Microsoft will have to build something better than V8,” Bak says. Most tech watchers doubt that they will manage to any time soon: in tests, V8 processes JavaScript 56 times faster than the most used version of Internet Explorer. “We started with high benchmarks,” says Bak. Then he adds, modestly: “It’s been an OK success.”

Even if the Chrome comic didn’t launch Bak into instant stardom, his profile has been rising over the past few months. More and more people want to know about the man behind Chrome. He would rather be writing virtual machines than running the Aarhus office, and he’d rather be doing almost anything than talking to journalists, but that’s part of the game and he accepts it. That said, he’s still a long way off the heights of Facebook founder Mark Zuckerberg or Bill Gates. Did he get any fan mail after the comic came out, I ask? He laughs at the idea: “No. But I didn’t get any hate mail either.”

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
在现有省、市港口信息化系统进行有效整合基础上,借鉴新 一代的感知-传输-应用技术体系,实现对码头、船舶、货物、重 大危险源、危险货物装卸过程、航管航运等管理要素的全面感知、 有效传输和按需定制服务,为行政管理人员和相关单位及人员提 供高效的管理辅助,并为公众提供便捷、实时的水运信息服务。 建立信息整合、交换和共享机制,建立健全信息化管理支撑 体系,以及相关标准规范和安全保障体系;按照“绿色循环低碳” 交通的要求,搭建高效、弹性、高可扩展性的基于虚拟技术的信 息基础设施,支撑信息平台低成本运行,实现电子政务建设和服务模式的转变。 实现以感知港口、感知船舶、感知货物为手段,以港航智能 分析、科学决策、高效服务为目的和核心理念,构建“智慧港口”的发展体系。 结合“智慧港口”相关业务工作特点及信息化现状的实际情况,本项目具体建设目标为: 一张图(即GIS 地理信息服务平台) 在建设岸线、港口、港区、码头、泊位等港口主要基础资源图层上,建设GIS 地理信息服务平台,在此基础上依次接入和叠加规划建设、经营、安全、航管等相关业务应用专题数据,并叠 加动态数据,如 AIS/GPS/移动平台数据,逐步建成航运管理处 "一张图"。系统支持扩展框架,方便未来更多应用资源的逐步整合。 现场执法监管系统 基于港口(航管)执法基地建设规划,依托统一的执法区域 管理和数字化监控平台,通过加强对辖区内的监控,结合移动平 台,形成完整的多维路径和信息追踪,真正做到问题能发现、事态能控制、突发问题能解决。 运行监测和辅助决策系统 对区域港口与航运业务日常所需填报及监测的数据经过科 学归纳及分析,采用统一平台,消除重复的填报数据,进行企业 输入和自动录入,并进行系统智能判断,避免填入错误的数据, 输入的数据经过智能组合,自动生成各业务部门所需的数据报 表,包括字段、格式,都可以根据需要进行定制,同时满足扩展 性需要,当有新的业务监测数据表需要产生时,系统将分析新的 需求,将所需字段融合进入日常监测和决策辅助平台的统一平台中,并生成新的所需业务数据监测及决策表。 综合指挥调度系统 建设以港航应急指挥中心为枢纽,以各级管理部门和经营港 口企业为节点,快速调度、信息共享的通信网络,满足应急处置中所需要的信息采集、指挥调度和过程监控等通信保障任务。 设计思路 根据项目的建设目标和“智慧港口”信息化平台的总体框架、 设计思路、建设内容及保障措施,围绕业务协同、信息共享,充 分考虑各航运(港政)管理处内部管理的需求,平台采用“全面 整合、重点补充、突出共享、逐步完善”策略,加强重点区域或 运输通道交通基础设施、运载装备、运行环境的监测监控,完善 运行协调、应急处置通信手段,促进跨区域、跨部门信息共享和业务协同。 以“统筹协调、综合监管”为目标,以提供综合、动态、实 时、准确、实用的安全畅通和应急数据共享为核心,围绕“保畅通、抓安全、促应急"等实际需求来建设智慧港口信息化平台。 系统充分整合和利用航运管理处现有相关信息资源,以地理 信息技术、网络视频技术、互联网技术、移动通信技术、云计算 技术为支撑,结合航运管理处专网与行业数据交换平台,构建航 运管理处与各部门之间智慧、畅通、安全、高效、绿色低碳的智 慧港口信息化平台。 系统充分考虑航运管理处安全法规及安全职责今后的变化 与发展趋势,应用目前主流的、成熟的应用技术,内联外引,优势互补,使系统建设具备良好的开放性、扩展性、可维护性。
提供的源码资源涵盖了安卓应用、小程序、Python应用和Java应用等多个领域,每个领域都包含了丰富的实例和项目。这些源码都是基于各自平台的最新技术和标准编写,确保了在对应环境下能够无缝运行。同时,源码中配备了详细的注释和文档,帮助用户快速理解代码结构和实现逻辑。 适用人群: 这些源码资源特别适合大学生群体。无论你是计算机相关专业的学生,还是对其他领域编程感兴趣的学生,这些资源都能为你提供宝贵的学习和实践机会。通过学习和运行这些源码,你可以掌握各平台开发的基础知识,提升编程能力和项目实战经验。 使用场景及目标: 在学习阶段,你可以利用这些源码资源进行课程实践、课外项目或毕业设计。通过分析和运行源码,你将深入了解各平台开发的技术细节和最佳实践,逐步培养起自己的项目开发和问题解决能力。此外,在求职或创业过程中,具备跨平台开发能力的大学生将更具竞争力。 其他说明: 为了确保源码资源的可运行性和易用性,特别注意了以下几点:首先,每份源码都提供了详细的运行环境和依赖说明,确保用户能够轻松搭建起开发环境;其次,源码中的注释和文档都非常完善,方便用户快速上手和理解代码;最后,我会定期更新这些源码资源,以适应各平台技术的最新发展和市场需求。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值