Web 的历史（Chrome University 2019）
本页标题、字幕、摘要和阅读笔记为已保存的 AI 译文，可能有误。时间戳与来源一致，可展开查看原始字幕，并对照原视频核对。
Chris Wilson 追溯早期 Web、Mosaic 和浏览器大战，反思标准、兼容性以及塑造该平台的社区。
文字记录来源：YouTube上创作者上传的字幕。Vidleaf添加了AI标点；保留原始措辞和时间戳锚点。原始文字记录可在下方获取。
AI生成的摘要
在这场演讲中，Chris Wilson——一位长期参与 Web 平台、曾参与编写 Windows 版 NCSA Mosaic 并后来在 Chrome 工作的贡献者——追溯了 Web 从早期 1990 年代的开端，历经浏览器大战直至今天的历史。他描述了伊利诺伊大学早期原始互联网的状况、ARPANET 时代访问方式的限制，以及 Windows 版 NCSA Mosaic 在没有网络协议栈、版本控制或正式测试的情况下是如何构建的。他解释了 Web 的增长如何由小众内容的长尾以及让每个人都成为作者所推动，并讲述了 blink 和 marquee 标签、IE 4 中的动态 HTML、ActiveDesktop 以及 IE 5-6 时代等事件。演讲还涵盖了 Avalon/.NET Framework 3.0 的努力、混搭应用的兴起、WHATWG 的成立、来自 Internet Explorer 7 的教训、移动革命、Web 2.0 以及渐进式 Web 应用。他总结说，与其把 Web 视为已经完成，我们应当让它适应事物的自然秩序，尊重用户、平台和社区，并做最好的倾听者，而不是房间里最聪明的人。
根据文字记录生成。请对照原始视频检查链接段落。
带时间戳的章节摘要
Web 历史与浏览器大战简介
Chris Wilson 的 Web 平台职业生涯
- [0:55] Chris Wilson 自我介绍为一名长期参与 Web 平台的贡献者。
- [1:00] 他 26 多年前开始从事 Web 平台的工作。
- [1:02] 他参与编写了 Windows 版 NCSA Mosaic，这是继 Tim Berners Lee 之后第一个面向大众市场的浏览器。
- [1:10] 他曾担任工程师、PM、首席 PM、GPM 和开发者关系倡导者等职务。
- [1:16] 他目前是 Chrome 中 TPGM 团队的成员。
- [1:19] 他曾在四种不同的浏览器上工作过，自 2010 年起成为 Google 员工，大约从 Chrome 版本 6 开始。
- [1:39] 他谦逊地指出，自己并不是房间里最聪明的人，但经常身处事情发生的房间。
- [1:50] 他请观众回想 1988 年，那时他进入伊利诺伊大学。
早期互联网与代际变迁
- [2:00] 在 1988 年，互联网几乎还不存在，在学术界仍被称为 ARPANET。
- [2:24] 他那一届入学本科生默认没有电子邮件账户；学生必须亲自到计算机实验室申请一个。
- [2:42] 大型机访问时间被限制为每周七小时，他经常把这些时间花在玩 Ultimate Larn 上。
- [3:00] 工程专业学生在另一台大型机上获得了第二个不受限制的账户。
- [3:09] 他的第一台互联网终端是一台淘汰的 HP 2622A，带有集成热敏打印机。
- [3:26] 他通过 2,400 波特的调制解调器连接到伊利诺伊大学系统，大约比他手机的 LTE 慢 6,000 倍。
- [3:50] 早期互联网主要是文本：电子邮件、Usenet、IRC 和 Gopher，FTP 主要用于共享软件。
- [4:21] 你年轻时存在的技术感觉是正常的，而 15 岁到 35 岁之间的发明则感觉是新的、值得作为职业的。
- [4:47] 与其把 Web 视为已经完成而加以否定，挑战在于让它适应事物的自然秩序，并想象它能成为什么。
1991 年 Marc Andreessen 在 NCSA
为 Windows 构建 NCSA Mosaic
- [6:20] 几个人创建了一款名为 Mosaic 的 X Windows 软件，用来访问由瑞士的一个人发明的万维网。
- [6:33] 万维网使用了一种名为 HTML 的原型文档语言。
- [6:40] 演讲者参与编写了 Mosaic 的 Windows 版本，这占据了他接下来 26 年的生活。
- [6:42] NCSA Mosaic 有三个完全不同的版本（Mac、PC Windows 和 X Windows），它们完全不共享代码。
- [7:08] Windows 缺乏内置的网络支持、套接字和 TCP/IP，因此团队编写了自己的网络协议栈和网卡设备驱动程序。
- [7:44] 演讲者亲自调试了 TCP/IP 回退算法。
- [7:52] 他们为 Windows 构建了 HTML 解析和渲染功能。
- [7:57] NCSA 有发布大量测试版的传统，通常在一台机器上构建后立即发布。
早期 Mosaic 开发及其挑战
- [8:17] Windows 版 Mosaic 首次上传到 FTP 服务器，一周内达到了 1,000 次下载。
- [8:27] 到 2011 年，Firefox 在几分之一秒内就达到了 1,000 次下载，显示了规模上的差异。
- [8:45] 尽管 DOOM 在同一年发布，团队仍然继续开发 Mosaic，因为他们还是大学生。
- [8:55] NCSA 的章程旨在促进教育和研究，这使得团队能够在其小组章程之外探索和构建网络浏览器。
- [9:20] 谷歌的灵活性与 NCSA 类似，演讲者对此表示赞赏。
- [9:29] Mosaic 团队由于缺乏知识、支持和商业计划而犯了一些愚蠢的错误。
- [9:46] 演讲者的计算机科学学位缺乏用户体验和软件测试理论的内容。
- [9:56] 没有版本控制系统或网络驱动器，两位开发者通过 zip 磁盘手动共享代码。
早期网络与重叠标签
- [10:25] 演讲者个人承担了在早期网络中实现重叠粗体和斜体标签的责任。
- [10:43] Chrome 和其他浏览器仍然支持重叠标签，其实现方式不违反文档规范。
- [11:02] 大约在 1993 年，早期网络之所以引人注目，是因为它提供了获取大量信息的途径。
- [11:17] 谷歌的使命是组织全球信息，使其普遍可访问且有用。
- [11:30] 当时世界上大部分信息都不在互联网上，甚至不在数字形式中，需要去图书馆。
- [11:57] 网络平台的 LICE 缩写是可识别的，但信息尚未真正可索引。
- [12:06] 一本大约在 1993 年出版的纸质书列出了 URL 及其描述。
- [12:34] 在 NCSA，他们认识到了网络最酷的地方。
早期网络共享与长尾
- [12:41] 目标是让每个人都成为作者，但大多数系统并非设计为让任何人都能架设服务器并共享信息。
- [12:51] Gopher 客户端很容易获取，但 Gopher 服务器软件很昂贵，因此主要由大学和私营企业运行。
- [13:08] 在 NCSA，他们实现了一些鼓励信息共享的功能，包括 1993 中的群组注释功能。
- [13:32] 他们认为网络服务器软件应该是免费的，每个人都应该在自己的机器上运行服务器。
- [13:49] 演讲者在 NCSA 的 PC 上运行了一个全球可访问的网络服务器，任何人都可以通过 FTP 进入。
- [14:00] 他和朋友们使用 NCSA PC Telnet 代码编写了一款网络太空狗斗游戏，促成了早期的局域网聚会。
- [14:36] 有很多古怪的内容，比如檀香山社区学院的 Kevin Hughes 将恐龙博物馆的照片放到了网上。
- [15:06] 网络的增长是由长尾驱动的：大量个体兴趣较低的内容，其总和与热门内容的受欢迎程度相当。
从迪吉里杜管到尤克里里：小众在线社区
- [16:04] 1996 年，演讲者上了一门关于演奏和制作迪吉里杜管的课程。
- [16:17] 他创建了一个关于如何制作竹制迪吉里杜管的网页，托管在 GeoCities 上。
- [16:37] 该网页使用了 ASCII 艺术，因为他没有数码相机，那是佳能 Digital Rebel 问世七年前。
- [16:50] 他在页面上留下了他的微软电子邮件地址，该页面一直保留到 2009 年 GeoCities 关闭。
- [17:03] 13 年来，他每月都会收到人们的电子邮件，询问在哪里可以买到生竹子，比如在芬兰。
- [17:18] 该页面仍然可以访问，URL 在演讲者的笔记中，尽管他对 artwork 感到羞愧。
- [17:53] 最近，他开始制作尤克里里，在网上购买材料和工具，观看 YouTube 视频，并在论坛上交流心得。
- [18:19] 他发现网上信息的丰富性，比如 eBay 上关于尤克里里木材的数百条结果，令人惊叹，并表明了一种新的自然秩序。
互联网加速人际互动
Mosaic 团队离职与 Internet in a Box
- [19:14] 1994 年，Mosaic 核心团队几乎同时离开了 NCSA。
- [19:23] Mark Andreessen 在前一年就已经离开了。
- [19:26] 演讲者辞职并搬到西雅图从事另一份工作。
- [19:30] Mark Andreessen 与 Jim Clark 一起回来，在工程团队解散之前招募了其余成员。
- [19:45] 演讲者加入了 SPRY，该公司构建了一款名为 Internet in a Box 的产品。
- [20:01] Internet in a Box 打包了连接互联网所需的一切。
- [20:07] 该软件包包含一个 Usenet 浏览器、一个电子邮件系统、一个 Gopher 客户端和一个网页浏览器。
- [20:15] 当时人们仍不清楚万维网是否会胜过其他协议。
SPRY、Spyglass 与加入微软 IE
- [20:35] 演讲者避免深入讨论 SPRY，因为这家公司的失败是有充分理由的。
- [20:44] SPRY 和 Spyglass 是完全不同的两家公司。
- [20:49] 离开 SPRY 一年后，演讲者加入了微软的 Internet Explorer 团队。
- [20:55] NCSA 将其代码授权给 Spyglass，因为 NCSA 不想涉足软件授权业务。
- [21:06] Spyglass 将授权代码转售给他人，微软则是从 Spyglass 获得授权。
- [21:15] Spyglass 声称它从头重写了所有代码，但演讲者发现其中大部分都很眼熟。
- [21:29] 这些代码与演讲者写过的代码有着相同的怪癖，尽管这些怪癖未必值得自豪。
- [21:38] 演讲者加入 IE 团队时，正值 IE 2.0 即将发布。
Netscape、Windows 与浏览器大战
Blink 标签与浏览器大战
Marquee 标签与 Google 彩蛋
IE 对 Netscape：布局、CSS 与签入熊
- [25:27] IE 在窗口大小改变时动态布局页面，这个系统是演讲者为 NCSA Mosaic 编写的。
- [25:41] Mosaic 的布局将文本拆分成永远不会重新合并的片段，因此缩小窗口会增加内存使用量。
- [26:12] Netscape Navigator 在窗口大小改变时从网络重新加载页面，导致表单字段数据丢失。
- [26:40] Netscape 开始跨页面加载进行缓存，正是为了避免在调整窗口大小时丢失表单数据。
- [26:55] 逐项功能对比显示，Netscape 追求的是比 IE 更廉价的功能。
- [27:06] 演讲者提议在 IE 3 中用 CSS 代替框架，随后首次在浏览器中实现了 CSS。
- [28:04] IE 3 的版本控制在并发签入时会失败，因此团队用一只实体泰迪熊作为信号量。
IE4 Trident 引擎与样式表
- [28:40] 在发布 IE 3 之后，团队开始规划 IE 4。
- [28:51] 微软为 IE 4 构建了一个全新的引擎，称为 Trident 引擎。
- [28:57] 演讲者第一次得知这个新引擎，是受邀参加 Forums Cube 团队的一场演讲。
- [29:12] 他的同事杰夫（Jeff）参加了那场演讲，回来后感到士气低落，说“我们完蛋了”，因为新引擎能在实时动态环境中做所有事情。
- [29:34] 杰夫只说对了一半，因为演讲者已经实现了样式表。
- [29:38] 一周后，演讲者向 Trident 团队做了一场演讲，展示他的样式表工作。
- [29:50] 一位听众请他不要发布某些功能，因为他们将不得不与之保持兼容。
- [29:57] 作为对那个请求的回应，演讲者决定加入三个功能而不是两个。
IE4 动态 HTML 与 ActiveDesktop
- [30:00] 他被邀请加入 IE 4 团队从事样式表工作，但被告知他将被安排在对象模型团队。
- [30:14] 这个时代的关键转变是，一切都变得可以动态编程。
- [30:21] 在 IE 4 之前，在 IE 3 和 Netscape Navigator 中，只有图像、超链接目标和输入字段可以被重新编程，布局无法改变。
- [30:50] 有了新系统，你可以更改 inner HTML、插入一个全新的文档，并修改文档对象模型。
- [31:02] 他跳过了一段 45 多分钟关于 hasLayout 的演讲，只指出那不是他的错。
- [31:16] Netscape Navigator 没有动态系统，而它后来成为 Mozilla 的新系统被推迟了。
- [31:29] Netscape 提议为可变内容新增一个 Layer 标签，而不是使用 CSS 定位，但微软坚持要做 CSS 定位。
- [31:50] 这场竞争的高潮是在 Windows 98 中发布 ActiveDesktop，它允许将 Web 内容拖放到桌面上，窗口装饰由 Web 内容完成。
- [32:07] 对于那些了解它的人来说，ActiveDesktop 是可怕的，因为它将一个非常重量级的系统放到了桌面上。
IE 5-6 时代与微软的失误
- [32:20] Alex Hauptmann 的团队为 Outlook Web Access 构建了一个数据传输控件，并在 IE 5 时代的 MSXML 中发布。
- [32:40] IE 5 以许多小版本发布（从 5.0 到 5.01D），同时试图与 Office 保持一致。
- [32:52] 在 IE 5 之后，微软主要只是重新架构，IE 5.5 引入了原生框架，IE 6 修复了 IE 5.5 破坏的东西。
- [33:13] 浏览器采用率在此期间达到顶峰，而微软对顶峰的处理很糟糕。
- [33:27] 在 IE 6 发布时，微软拥有最好的浏览器，比 Netscape Navigator 更好，而且 Mac 产品比 Windows 产品更好。
- [33:49] 当时的网络缺乏丰富的布局——没有堆叠或网格——尽管它很好地处理了流文本和表格。
- [34:03] 微软硬核的兼容性理念使得修复标准支持需要批准，即使它破坏了诸如旧游戏帮助页面之类的琐碎事情。
- [34:29] 网络并没有将开发者带回 Windows，导致微软质疑为何在其中投入如此之多。
Avalon、混搭与浏览器大战
Internet Explorer 7 的教训
- [35:50] 在 2004 年，微软意识到需要对其浏览器采取行动，从而导致了演讲者个人最引以为豪的 IE 7 发布。
- [36:03] 这种自豪感并非来自发布的内容，而是来自从零开始组建团队。
- [36:10] IE 7 在维基百科上列出的功能包括标签浏览、页面缩放、集成搜索框和源阅读器，而 Web 标准支持仅略有改善，仍然未能通过基本测试。
- [36:27] 团队不得不习惯被诋毁，包括一位冒充撒旦的博客评论者向演讲者提供工作。
- [36:48] 演讲者建议不要阅读 YouTube 评论或过于关注他人。
- [36:53] 演讲现在才讲到 Chrome 开始的时期，Peter 将转而讨论那个。
- [37:05] 微软继续只对平台而非浏览器进行最低限度的投资，这对他们并不奏效。
- [37:18] 来自 IE 的关键教训：不要在顶峰时自满，不要只关注竞争对手，那只适用于两个参与者的情况。
- [37:41] 团队试图避免怪异行为，关注细节，并构建大量测试页面以遵循规范。
- [37:51] 并非所有聪明人都在你的公司工作，不要忽视颠覆性因素。
移动革命与网络挑战
Web 2.0 与渐进式 Web 应用
Web 平台的普遍性与跨设备挑战
尊重用户并成为倾听者
[0:03] CHRIS WILSON：下午好。我在这里要谈谈网络的历史，从它在1990年代初的卑微起步，经过浏览器大战的高潮和低谷，直到今天。对我来说，这次演讲的很多内容都是怀旧。我希望有很多——看看历史对当今网络产生了什么影响。正如乔治·桑塔亚那所说，那些不能记住过去的人注定要重蹈覆辙。我们绝对不要那样。我将大量谈论Internet Explorer的历史。
[0:34] 你马上就会知道为什么。但我仍然相信，其中很多推动了我们走到今天。但就像梅尔·布鲁克斯的电影一样，我必须跳过很多。所以我今天整理的第一份幻灯片我认为大约有一个半小时长。希望我能讲完并准时结束。所以，嗨。我是Chris Wilson。我在网络平台上工作了超级长的时间。我26多年前开始。我合写了NCSA Mosaic的Windows版本，这是继Tim Berners Lee的浏览器之后第一个真正大众市场的浏览器。
[1:10] 我当过工程师、产品经理、首席产品经理、集团产品经理、开发者倡导者。我目前是Chrome的TPGM团队。我想我曾在四个不同的浏览器上工作过，而且自2010年以来一直是Google员工。顺便说一下，那是自Chrome版本6以来。Chrome版本6在我开始一周后发布。别误会。那听起来超级厉害。我不认为我是房间里最聪明的人，当然不是在这个房间里。
[1:43] 借用汉密尔顿的一句话，多年来我很多很多次身处事件发生的现场，这很酷。但是——所以我想让你们所有人把思绪拉回，对你们中的一些人来说，在你们出生之前，到1988年。1988年是我去伊利诺伊大学读本科的时候。为了给你们描绘当时的互联网，这张图表很棒。你实际上看不清标签，但1988它基本上就在这里。你会注意到它几乎不存在。
[2:16] 那时没有人真正听说过互联网。事实上，在学术圈它仍然通常被称为ARPANET。我入学的那一届本科生默认没有分配电子邮件账户。你实际上必须去计算机实验室，当面申请一个。而且，事实上，我们登录到我们的主机。就像，人们通常没有连接的能力。而且你在这个主机系统上每周有七小时的时间限制。
[2:47] 我通常会把这时间烧在玩Ultimate Larn上，因为你只有七小时。我通常会在头几天就烧完，然后直到周六早上才能再查邮件。幸运的是，工程专业的学生在另一台主机上获得了第二个不受时间限制的账户。所以显然，我通过了我的计算机科学课程。这是我的第一个互联网终端。它是我暑假工作时淘汰下来的终端。它是一台HP 2622A终端。
[3:20] 它顶部有一个集成的热敏打印机。太棒了。我通过一个当时来说快得冒烟的2,400波特调制解调器把它连接到伊利诺伊大学的系统。作为参考，我计算过我的手机整体LTE连接速度大约快6,000倍，在家用Wi-Fi时快60,000倍。或者大约是我在Mountain View这里酒店Wi-Fi速度的两倍。
[3:50] 但这只是一个文本终端。就像，互联网主要是文本。事实上，这是我在这里提出的观点之一，它真的就是电子邮件、Usenet、IRC、Gopher。FTP也很酷，但坦率地说，用得少得多，除了分享软件。现在别担心。我的整个演示不只是道格拉斯·亚当斯的引语。我想还有几句。但这真的——这是任何时候都要记住的事情。
[4:21] 任何在你出生时或你还很年轻时存在于世界上的东西都只是正常的。世界就是这样运作的。我有两个女儿。互联网就是世界运作的方式。她们甚至不去想它。移动设备？绝对。任何在你15岁到35岁之间发明的东西都是新的、令人兴奋的，而且你可能可以以此为职业。而互联网、网络，绝对是在我15岁到35岁之间发明的。现在，我不是真的在这里说，滚出我的草坪，你们这些年轻的毛头小子。
[4:52] 网络已经完成了。你能想到的一切都违背事物的自然秩序。挑战实际上在于，你如何接受它并使其能够适应事物的自然秩序。想想它未来能变成什么。因为否则，我在Chrome发布前就35岁了，那会是个问题。在1991年，我得到了一份兼职工作，在国家超级计算应用中心工作。这是我最后一次把它拼写出来。NCSA是五个最初的NSF超级计算中心之一，我们在NCSA内部的小组使命是构建软件工具，使研究人员能够在他们的桌面上使用超级计算机的能力。
[5:39] 所以我们做了Telnet。我们真的构建了Telnet。事实上，这就是我被雇来做的工作，在终端上工作。现在记住，这是在Windows 95之前。这是在Windows 95之前。没有TCP/IP网络栈。PC Telnet是DOS软件。我们最终不得不构建Windows软件。我们还做了可视化工具之类的东西。数据加载和格式化工具，诸如此类。
[6:11] 但当这个项目出现时，这正好契合，有几个人想出了这个叫Mosaic的X Windows软件，让你可以访问瑞士某个人想出的叫万维网的东西。使用了一种叫HTML的原型文档语言。那差不多——嗯，那是我接下来26年的生活。我合写了它的Windows版本。
[6:42] 顺便说一句，NCSA Mosaic 有三个版本：Mac、PC、Windows 和 X Windows。它们完全不同。它们根本不共享代码。我们会看彼此的代码，但跨平台软件，当时并不真的存在。还有，这彻底毁了我对“mosaic”这个词的感觉。如果你说“mosaic”这个词，我不会想到一件艺术品。但请记住，再说一次，我们在 Windows 上没有网络支持。Windows 没有内置的网络驱动。
[7:15] 比如，它们没有套接字。你可以买一个单独的软件包来添加它。即使是带网络的 Windows 3.11，我记不清确切的名称了。我想是 Windows for Work Groups。它没有内置 TCP/IP。没有套接字。它有网络，但通过 Novell 或其他什么东西。所以我们已经有了自己的网络栈。我们实际上真的为网卡编写了设备驱动。比如，我会调试这些东西。我曾经调试过 TCP/IP 回退算法。
[7:50] 于是我们在 Windows 上让它运行起来了。我们构建了 HTML 解析和渲染之类的东西，所有那一类东西。而 NCSA 有一个传统，就是发布大量大量的 beta 版本。基本上就是，在你自己的机器上构建，然后发布一个版本。我想我实际上发布了好几个调试版本，因为有一次我找不到一个 bug，结果当然是某个指针初始化的问题。但我们第一次把 Windows Mosaic 放到了 FTP 服务器上。
[8:20] 我记得，我们超级兴奋，因为一周后，我们的下载量达到了 1,000。现在，我想我在 2011 年做过这个演讲，我计算过 Firefox 达到 1,000 次下载用了多长时间，结果是以几分之一秒来衡量的。所以规模有点不同。但仍然，真正令人惊讶的是，游戏 DOOM 是同一年推出的，而我们仍然设法在 Mosaic 上完成了工作，因为我们是大学生。
[8:53] 我的意思是，我们是学生。NCSA 有一个很棒的总体章程，就是，嘿，去推动教育和研究。我们得以探索很多东西。如果那里没有这个，我们就不会去构建一个网页浏览器。当时这并不在我们软件工具组的章程里。我们的章程是构建图像可视化工具、Telnet 等等。这是其中一件事，是我与 Google 画出的一个平行之处，因为 Google 有很多这种灵活性。
[9:26] 这是我在这里工作时真正喜欢的一点。不过总的来说，我们在 Mosaic 里犯了一堆愚蠢的错误，因为我们并不真正知道自己在做什么。我们并没有得到很多支持。我们没有商业计划。我的意思是，很多互联网公司也没有商业计划，但我们真的没有，比如，我的计算机科学学位里没有用户体验课程。没有软件测试理论之类的课程。
[9:56] 我们甚至没有版本控制系统。比如，我们两个人一起做 Windows Mosaic。我们没有网络驱动器。所以实际上，我们会，比如，处理同一份代码，把它保存到 zip 磁盘上，走过办公室，把它插到另一个人的驱动器里，复制正确的文件，然后希望一切顺利。所以我们确实做了一些愚蠢的选择。其中一个我个人要负责的是这个。我个人要为早期网络中重叠的粗体和斜体标签能够正常工作负责。
[10:32] 出于某种原因，我觉得这会很酷。这是对所有常识和 SGML 结构化文档体面的肆意违反。顺便说一句，是的，我们在 Chrome 和可能其他所有浏览器中仍然支持这个。我们以一种有趣的方式来做，不会违反所有体面的东西。但为我辩护一下，尽管这辩护不怎么样，我当时觉得这会很酷。但早期的网络，甚至是真正早期的网络，因为记住，我是在大概 93 年左右。
[11:10] 它真的很有吸引力。它之所以有吸引力，是因为你可以访问所有这些信息。我的意思是，Google 的使命是组织世界上的信息，使其普遍可访问且有用。我就是之前在后面聊天的那个人，当时 Parisa 问了这个问题，因为它在我的幻灯片里出现了好几次。你必须记住，在那个时代，世界上的信息并不在互联网上。互联网就像，我们处在那个斜坡的低处，对吧？
[11:42] 很多信息甚至还没有以数字形式存在。比如，你必须去图书馆才能获取信息。当然，最终，任何看过大量信息并且知道我们通常如何看待网络平台的人，都会认出这里 LICE 缩写的一部分。但在这个阶段，它并不是真正可索引的。或者它是可索引的，但没有指向它的索引。事实上，我本来想带过来，在我的书架上，我有这本书。比如，一本装订的纸质书，里面实际上就是 URL 列表和对它们的描述。
[12:18] 它出版于，我想是 93 年。93 年或 94 年，我记不清是哪个了。它就是一本厚厚的书，里面写满了，嘿，这是你可以在 Honolulu Community College 网站之类的地方找到的东西。所以最关键的是，在 NCSA 我们有这个——我们认识到，这个网络东西最酷的地方在于每个人都可以成为作者，因为当时大多数系统并不是真正为任何人搭建服务器和分享信息而设计的。
[12:51] 尤其是 Gopher。比如，Gopher 客户端很容易获取。Gopher 服务器软件你得花一大笔钱。基本上只有大学或私营企业运行它，因为运行这个软件太贵了。所以，我们实际上在 NCSA 实现了一堆东西，试图鼓励这种信息分享。我们实际上，甚至在 1993 中，我们实现了一个群组注释功能。
[13:21] 就像，你可以给网页添加注释，然后你们组里任何共享同一个注释服务器的人，当他们访问相同的网页时，就会看到你的注释。我们还有一个想法，就是网页服务器软件应该是免费的，每个人都应该在自己的机器上运行一个服务器。现在，把这个放在背景下看，这与我们今天所处的位置之间，还隔着好几代大规模的安全问题。实际上，我在NCSA办公室的PC上运行过一个网页服务器。
[13:54] 它是全球可访问的。我是说，真的任何人都可以通过FTP进入我的个人电脑。事实上，我们写了一个网络太空狗斗游戏。我和大学里的一群朋友，我们借用了NCSA的PC Telnet代码来做这个。在我们玩了一段时间之后，比如，我们把它运行起来了。那感觉就像，太棒了。那些早期的局域网派对。太棒了。在我们运行了一段时间后，我意识到我从未禁用PC Telnet代码中的FTP服务器。
[14:26] 所以果然，我可以比如，在我朋友玩游戏的时候FTP进入他的机器，然后，你知道，开始一个大下载。他并不真的喜欢那样。但酷的是那里有很多古怪的内容。比如，这在当时是开创性的，因为你无法访问这些内容。比如，有一个叫Kevin Hughes的人，来自檀香山社区学院，他们在这所檀香山的社区学院里有一个非常酷的恐龙博物馆。所以他想，哦，这太棒了。
[14:58] 我会用我的数码相机拍一些照片放到网上。他确实这么做了。然后就像，你只会得到这种奇怪的东西。而这，比任何事情都更能让我认为，推动了网络增长的是长尾这个概念。谁以前没听说过长尾？只是——好吧，所以有几个，这很好。这就是大量内容所在的地方——总体人口都在这条尾巴里。不幸的是，颜色搞乱了。但就像，这里的所有这些东西，按兴趣衡量，和最受欢迎的东西一样受欢迎。
[15:35] 所以另一种看待这个问题的方式是，网络是不可思议的，因为人们对不常见的话题超级感兴趣，甚至有时比泰勒·斯威夫特的最新视频还感兴趣。顺便说一句，那很棒。这在今天被认为是理所当然的。就像，这是那种你点头说，是啊，随便的事情之一。这在当时是新的，因为在'90年代初你无法真正接触到长尾。事实上，在'90年代初，或者'90年代中期，实际上，在1996年，我上了一门学习吹迪吉里杜管的课。
[16:12] 课程的一部分是如何制作一个。我当时想，哦，这真的很酷，然后我建了一个网页，如何制作竹制迪吉里杜管。顺便说一句，这很简单。你差不多就是在上面戳个洞。但你们有多少人记得GeoCities？对了。怀旧爱好者，我喜欢。我在GeoCities上建了一个网站，讲如何用竹子制作迪吉里杜管，还配了ASCII艺术，因为我还没有数码相机。
[16:44] 作为参考，这是佳能推出Digital Rebel的七年前。所以它真的不那么受欢迎，我把我的微软电子邮件地址放在上面。是的，这在今天看来是疯狂的做法，但我做了。这个页面一直保留到2009年GeoCities关闭。在那整个期间，13年里，至少每个月一次，我会收到某人的电子邮件说，嘿，这很棒。我想知道你是否知道在芬兰这里哪里可以弄到生竹子。
[17:18] 顺便说一句，这个页面仍然可以访问。如果你真的想看，URL在本页的演讲者备注中，但我现在不打算去访问它，因为我对那里的 artwork 有点羞愧。但我讲这个故事不是因为我认为你们都对制作竹制迪吉里杜管感兴趣，尽管我很乐意谈论那个。你们中更少的人实际上对在加利福尼亚这里哪里可以弄到生竹子的更精细细节感兴趣。我确实知道，因为我确实在这里住过一段时间。
[17:49] 但你可能有一些同样不常见的兴趣。事实上，相比之下，过去几年，我开始在业余时间制作尤克里里。我在网上购买材料和工具。我在YouTube上观看如何正确弯曲侧板或那个东西的视频。我在论坛上比较关于不同木材选择的笔记，等等，在eBay上浏览异国木材。这是真的。比如，我会在eBay上搜索尤克里里木材。
[18:24] 而且不是像，五页。有像，数百个结果。我在显示我的年龄，因为我觉得这很神奇。比如，这正在颠覆，你所拥有的信息访问权。这是一个大规模的新自然秩序。这引出了我几十年来关于我职业生涯所说的话，即网络和互联网只是帮助人类互动发生得更快，更少的护栏，更少的路障。
[18:54] 顺便说一句，我曾经认为这是一件无条件的好事。我不再这么认为了。所以这有点预示，要小心你如何促成人类互动。但它确实消除了地理障碍和信息障碍。所以无论如何，回到1994年，核心Mosaic团队几乎同时离开了NCSA。马克·安德森前一年已经离开了。
[19:26] 我辞职并前往西雅图接受另一份工作。然后马克和吉姆·克拉克回来了，在其余工程团队离开并各奔东西之前把他们挖走了，因为他们看到我是第一个离开的，但我不会是最后一个。但我去了这家叫SPRY的公司。他们做了一个叫Internet in a Box的产品。我的书架上确实也有一个。是的，整个互联网装在一个盒子里。
[19:58] 但这挺酷的，因为这是你连接互联网所需的全套东西。再说一次，在当时，这相当酷。它有一个 Usenet 浏览器。它有一个电子邮件系统。还有一个 Gopher 客户端。它也有一个网页浏览器。顺便说一句，当时还不清楚网页就是赢家。它拥有所有这些。就像，当我在准备这个演讲时，我在 Mac 上点了 Command 标签，结果 literally 唯一在运行的东西就是两个浏览器副本和计算器。
[20:31] 而这只是因为点击图标更容易打开计算器。现在，我不想过多谈论 SPRY 本身，因为他们消失是有充分理由的。顺便说一句，它不是 Spyglass。Spyglass 是一家完全不同的公司。事实上，一年后我离开了 SPRY，加入了微软和 Internet Explorer 团队。Spyglass 实际上是 NCSA 将其代码授权给的那家公司，因为他们意识到软件授权业务并不是 NCSA 真正想从事的业务。
[21:06] 然后 Spyglass 将其转售给其他所有人，而微软实际上是从 Spyglass 那里获得授权的。Spyglass 说他们从头重写了所有代码。我只想说，很多代码看起来非常熟悉，而且很多架构选择——是的，它有一些和我写的代码相同的特质。并不是说我一定为此感到自豪，但确实是一样的。
[21:38] 但我在我们发布 IE 2.0 之前加入了 IE 团队，作为背景。我相信你们中有些人可能以前听过这句话。马克·安德森曾被引述说，网景将把 Windows 降级为一组调试不良的设备驱动程序。顺便说一句，为他辩护一下，马克实际上说这是鲍勃·梅特卡夫说的，他只是在转发。嗯，引用它，因为那时还没有 JavaScript。
[22:09] 那时还没有 Twitter。这看起来可能像是在廉价攻击微软。实际上并不是，因为我当时并不相信。我继续为微软工作了 15 年。我现在甚至也不相信，因为那些设备驱动程序在这一点上调试得非常好。但我不认为我们任何人预料到了这句话所预示的事情，即世界将变成网络平台，软件运行在它之上，而不是一大堆软件运行在 Windows 之上。
[22:44] 这确实引发了浏览器大战。而我对浏览器大战的丑陋之处最喜欢的例子是 blink 标签。有多少人听说过 blink 标签是如何发明的故事？哇，好的。所以这个例子相当不错。我没有参与这件事。我当时不在事情发生的那个房间里。blink 标签的诞生是因为一些网景工程师某晚出去喝酒。我没开玩笑。这在维基百科上。去查查吧。
[23:15] 他们中的一个，或者更多，说，哦天哪，我们应该做一个让所有东西都闪烁的标签。他们出去喝酒了，所以其中一个决定回办公室，第二天早上，向同事们展示了 blink 标签。现在，在微软，我们讨厌 blink 标签。我们想，天哪，你为什么要让——你为什么要这样做？就像你要，我不知道，触发对闪烁灯光敏感的人之类的。
[23:46] 这太可怕了。事实上，当网景团队要求 CSS 包含 text-decoration: blink 时，我说好吧。我们会解析它。我们会应用它，但我们不能被强迫让它真正闪烁。至少它在 CSS1 规范里。你实际上并不被要求让东西在视觉上闪烁。不过，我们仍然必须在闪烁上胜过他们，这就是 marquee 标签的由来。对于 marquee 标签，只需在 Google 搜索中搜索 marquee tag。
[24:21] 这实际上很棒，因为它现在有我在 Google 搜索中最喜欢的彩蛋，因为它实际上复制了 marquee 标签。就像，标签结果开始来回滚动。这基本上就是 marquee 所做的。它让文本来回滚动。这个笑话最终实际上开到了我们 IE 团队自己身上，因为我们也让它垂直滚动并垂直堆叠文本。就像 marquee，你知道，当你走在时代广场或什么地方，有垂直文本。
[24:54] 显然，这在韩国非常流行，因为它符合当时他们的文本和字体的工作方式，并且在开发韩文文本时很有用。我们实际上十多年都无法移除它，因为它是如此广泛地使用，我们会破坏很多内容。现在，在 1996 年我们发布了 IE 3，所以这就是我们所处的时代。
[25:24] 大约在这个时候，重要的是要理解，IE 实际上会动态布局页面。就像，如果你调整窗口大小，它会重新布局。这实际上就是我在 NCSA Mosaic 中编写原始渲染布局系统的方式。顺便说一句，这也是我之前谈到的特质，就是我会将文本分成多个连续段。当你缩窄窗口时，它必须在不同的地方断开，而且——就像，这些段永远不会重新组合。它们只会堆叠。
[25:54] 所以就像，如果你拉伸它——如果你把窗口一直挤到最小，它会占用稍微多一点的内存，并在整个系统中有更多的段。他们有同样的问题。另一方面，网景导航器，当你调整窗口大小时，它会 literally 从网络重新加载页面。甚至不是从磁盘。就像，磁盘缓存还要一两年才开始成为现实。
[26:25] 所以他们真的会去重新加载页面。事实上，如果页面上有表单字段，也许你发现其中一个看不见，然后调整窗口大小，它就会重新加载页面并丢失所有内容。正是因为这个原因，他们开始跨页面加载缓存内容。但我们做了这种功能对功能的比较，但越来越明显的是，他们——他们追求的是比我们更廉价的功能。
[27:00] 我们确实在 JavaScript 中、在表格上、在字体标签上做了功能对功能的比较。我实际上是在浏览器中首先实现 CSS 的人。这是因为我的老板真的走进我的办公室说，嘿，我们正在规划 IE 3 的功能。我们想让你做框架，因为我们还没做框架，iframe、框架集等等。我说，嘿，那会很酷。但有这个东西叫 CSS。
[27:30] Netscape 甚至还没看这个。它会超级酷。你可以做所有这些漂亮的视觉东西。他说，哦，让我想想。1/2 小时后回来说，是的，去做吧。这就是我们如何在浏览器中得到 CSS 的。我之前提到过编码，编码质量，比如说，软件系统。在这一点上，我们至少有了版本控制。比如，我们有网络驱动器。
[28:01] 但在 IE 3 时代，如果多个人同时尝试签入，我们的版本控制系统就不太管用，因为我们经常签入许多不同的文件。我们有一个我们称之为签入熊的东西。这实际上是一个物理泰迪熊。它坐在走廊里的一块白板旁边。如果你需要签入，你必须去拿熊，在白板上写下你的名字，拿走熊，当你签入时熊必须坐在你的桌子上，然后你回去，如果别人在你的名字下面写了名字，你就去把熊给他们。
[28:36] 我想这是一个有趣的信号量。但在我们发布 IE 3 之后，我们开始展望 IE 4。在微软，有了 IE 4，我们实际上构建了一个全新的引擎，Trident 引擎，后来被称为 Trident 引擎。我第一次发现这件事是在我们被邀请去听一个叫 Forums Cube Team 的团体的演讲时。不知道那是从哪来的。有传言说他们在构建什么东西，而我没机会去。
[29:10] 我正忙着做别的事。但另一个在渲染引擎上工作的人，我的朋友杰夫，他去了。他回来了。他走进我的办公室，他非常非常沮丧。我说，怎么样？他说，我们完蛋了。他们能做一切。他们能编辑。他们能改变东西。就像，这是一个完全实时的动态环境。我们失业了。他说对了一半，因为我做了样式表。大约一周后，我给 Trident 团队做了一个演讲，展示了我在样式表上做的所有东西。
[29:44] 我说，这个能，这个能。我希望在我们发布之前加入这两个功能。现在，真的，观众中有人说，你能不能不要，因为你发布的任何东西，我们都必须兼容。现在，就为了那个，是三个功能。所以他们让我转到 IE 4 团队，做样式表。当我被邀请加入时，我被告知我会在对象模型团队。我说，什么？JavaScript 团队？你让我做样式表。但这正是这个时代的关键，一切都变得可动态编程。
[30:21] 在此之前，在 IE 3 中，一直到 IE 3，并且在 Netscape Navigator 中仍然如此，你只能重新编程图像。不是大小，因为你不能改变布局，但你可以替换视觉内容，特定超链接指向的链接，输入字段。没有别的。没有任何改变文档布局的东西。你唯一能改变视觉效果的方式是输入字段和图像。突然之间，你可以重做一切。
[30:52] 我的意思是，你可以改变 inner HTML 并在那里放入一个全新的文档。你可以改变文档对象模型中的东西。有几样东西你不能动态改变。这里有一个关于 hasLayout 的 45 分钟以上的演讲，我就直接跳过了，只是说这真的不是我的错。人们有时确实这么说。不是的。非常重要的是要理解 Netscape Navigator 没有动态系统。他们不能动态地改变所有东西，比如，他们的新系统，后来成为 Mozilla 的，被延迟了。
[31:29] 为了应对这一点，他们提议，嘿，我们应该有一个叫做 Layer 的新标签，而不是通过对象模型实时改变一切。你可以把变化的东西放在一个层里。但整个 CSS 定位的东西，我们不要做那个。我们说，不，我想我们要做那个。有很多来回的争论。我认为这一切在我们发布 Windows 98 中的 ActiveDesktop 时达到了高潮。这是因为你突然可以把 Web 内容放到桌面上，而那里所有的窗口装饰实际上都是用 Web 内容完成的。
[32:07] 这对我们这些真正知道发生了什么的人来说是可怕的，因为这是一个非常重量级的系统被放入一个非常低级的系统。但这也是 Ajax 黎明的时候，对吧？这是，Alex Hauptmann，一个我后来在 IE 一起工作的人，他们需要一个用于 Outlook Web Access 的数据传输系统。所以他们想出了这个控件，在 MSXML 中发布，这是在 IE 5 的时间框架内发布的。
[32:38] 我不确定是IE的哪个5版本，因为实际上我们有IE 5.0、5.01、5.01A、5.01B、5.01C和5.01D。我们试图与Office一起转变。尝试了几次。之后，我们在微软这里有点磕磕绊绊。我们主要只是在重新架构。比如，IE 5.5到这个原生框架的东西。而IE 6修复了我们在IE 5.5中破坏的所有东西。差不多就是这样。真的。我们真的不知道该怎么办。
[33:09] 很大程度上是因为这张图表。这是浏览器采用率，在这段时间内。你会注意到那里有一个不错的峰值，而大多数人在峰值时表现不佳。尤其是微软，但大多数人在峰值时都表现不佳。但当我们发布IE 6时，我们正好在这里。我们拥有地球上最好的浏览器。我的意思是，我们比Netscape Navigator好得多，虽然我承认这有点偏见。
[33:41] 我们的Mac产品实际上比我们的Windows产品更好。或者Mac团队在某处鼓掌，他们甚至不知道为什么。但Web实际上并没有丰富的布局。它在流式文本上做得很好。在表格上做得很好。但当时它不支持堆叠，也不支持网格，这有点糟糕。兼容性对我们来说成了一个真正的问题，特别是因为微软有这种非常非常硬核的兼容性理念。
[34:12] 我记得为了修复我们的标准支持，不得不请求批准破坏某些东西，但这会破坏Microsoft Cart Precision Racing帮助页面中的某些内容，那是一款我们大约三年前发布的游戏。总的来说，Web并没有引导开发者回到Windows，微软开始质疑，为什么我们要为一个不能给我们带来更多开发者的事情做所有这些。我们已经拥有了所有用户，那为什么我们需要这样做。
[34:45] 他们只是想保住开发者市场。所以我们创建了这个Avalon项目，它后来变成了dotnet框架3.0。而且我——至少还有另一个45分钟的演讲在里面。当然，这最终导致他们也失去了那个市场，然后衰退了。当然，与此同时，世界一直在前进，对吧？这种混搭应用的模式变得越来越重要。我在内部写了一篇关于混搭的白皮书。
[35:16] 这基本上就是多个组件和数据开始汇聚在一起。再次，这在今天看来很自然。但当时你有同一个系统，里面有芝加哥犯罪统计数据和地图软件，而且你可以让它们动态地协同工作，这个想法在当时相当了不起。当然，WebKit开始获得关注。Firefox也在获得关注。而WHATWG也在这附近成立了，因为W3C有点迷失了方向。
[35:46] 那里有几个小时的演讲。在2004年，微软终于醒悟了，说，哦，等一下。我们需要在这里做点什么。而这实际上是我个人最引以为豪的版本。不是因为我们实际发布了什么，而是因为我们不得不从几乎零开始建立一个团队。不幸的是，你读到——这是维基百科上关于IE 7的页面，它大概说，新功能，包括标签浏览和页面缩放、集成搜索框、源阅读器。
[36:22] 哦，对了，Web标准支持好了一点，但它确实没有通过基本测试。而且——在这个阶段我们不得不习惯被诋毁。我确实在博客评论中遇到过有人冒充撒旦，当时给我提供了一份工作。问我赚多少钱，以及我是否想要一份工作。我有点担心，所以我没有删除那条帖子，因为你永远不知道。但不要读YouTube评论。不要太在意别人。
[36:53] 我要指出，我们现在才进入Chrome开始的时期。所以我实际上不打算涵盖这些，因为Peter会比我做得更好。但我要说，微软继续对平台进行最低限度的投资。不是浏览器，而是平台。这对他们来说效果不太好。而这一切很大程度上让我得出了从IE经历中学到的教训。
[37:23] 不要仅仅因为你处于那个堆的顶端就变得自满，Chrome肯定可以在这方面学到一些东西。不要关注竞争对手是其中很大一部分。当只有你们两个的时候，这还行，但当有很多不同的人和很多事情时，就不那么好了。我们实际上相当擅长不做古怪的事情。我们试着注意。我们试着构建大量测试页面，并确保我们遵循规范。但最重要的是，并不是所有聪明的人都在你的公司工作。
[37:55] 当然，不要忽视像移动革命这样的颠覆性因素，它大约也在这个时候出现了，对吧？这也给我们在Chrome上带来了一些挑战。但这是一件大事，对吧？比如，我在12年里从拥有这个摩托罗拉Startac——我向你保证它刚出来时超级性感。它是当时最好的手机。我喜欢那部手机。直到我把它掉进华盛顿湖，到拥有一个iPhone。对吧？而iPhone，它有所有这些传感器，触摸屏超级吸引人，而且里面有如此强大的力量。
[38:32] 顺便说一句，iPhone 发布时我还在用 35。但我还是设法适应了，因为我记得两年后我说过，对，基线。我的手机现在必须取代我的吉他调音器。就像，它就必须能用。我不再随身带着吉他调音器了。我办公室里有一把吉他，我对音高足够敏感，所以我希望它能正常工作。不幸的是，当时 Web 并不只是移动平台。那本来会很好，但坦率地说，在那个阶段，Web 仍然是由 768 为 1,024 设计的。
[39:07] 字面上，它是硬编码在网页里的。当 Apple 提出他们那些关于如何重新映射到其设备上的有些古怪的规则时，他们正是依赖这一点。而且，为了让大多数页面看起来正确，他们其实并没有错。但它并不真正开放支持触摸输入。偶尔你需要键盘，而网络仍然相当不稳定。就像，人们并没有预料到这一点。而这超级重要。这实际上也来自那个时期前后。
[39:39] Ben Galbraith，早在他去 Google 工作之前，就在一次会议上说过这句话。他说，Web 2.0 不是关于一组技术。它是关于关心你的用户体验，而这就是当时的大演进，人们开始真正关心浏览器中提供的体验。在那之前，他们其实并不关心。在那之后，我们实际上又有了另一个版本，就是几年前我们不得不推出渐进式 Web 应用横幅的时候，我们真的必须关注这样一个事实：带宽仍然是必需的。
[40:15] 就像，如果你不知道自己有连接，Web 就运行得不好。我做过很多关于这个的演讲。但此时，我希望大家关注的是，我确信 Web 平台仍然是那个通用平台的一大原因，是那些对能力的访问正在迎头赶上。我们只需要在安全和隐私以及用户体验方面超级小心。而且，最重要的是，这个平台在其他设备上如何运作。
[40:46] 这也是 Microsoft 掉入的陷阱之一。因为即使 Microsoft 有两个浏览器团队，一个 Mac 团队和一个 Windows 团队，Mac 团队也被放在角落里独自待着。他们没有整合。他们没有考虑这件事。而且，就像我是沉浸式 Web 工作组联合主席。我们必须考虑 Magic Leap 的 AR 头显以及 WebXR 在其上如何运作，尽管据我所知 Google 目前并没有在构建 AR 头显。所以这有点重要。对此的指导，实际上，这是 Google 101，对吧？
[41:22] 尊重用户，尊重平台，尊重社区。不要做房间里最聪明的人。对于你们中任何从事标准工作的人，要做最好的倾听者。这是应对这件事好得多的方式。正如 Parisa 今天早些时候提到的，这是我们在 Chrome 团队的使命。顺便说一句，总的来说，这就是把我带到 Google 的原因。就像，这是 Google DNA 中很强的一部分。这是 Chrome 团队 DNA 中很强的一部分。这也正是我留在这里的原因。
[41:54] 说到这里，我想用我最后两句 Douglas Adams 的引语来结束。谢谢。[音乐播放]
查看英文原始字幕
[0:03] CHRIS WILSON: Good afternoon. I'm here to talk about the history of the web, from its humble beginnings in the early 1990s through the high and low points in the browser wars to today. And a lot of this talk, for me personally, is nostalgia. I hope there's a lot of-- see what impact history had on today's web. As George Santayana said, those who cannot remember the past are condemned to repeat it. Let's definitely not do that. I'm going to talk a lot about Internet Explorer's history.
[0:34] You'll find out why in a second. But I still believe a lot of this drove getting us where we are today. But much like Mel Brooks' movie, I have to skip a lot. So the first deck I pulled together for today I think was about an hour and half long. Hopefully I'll make it through and land on time. So hi. I'm Chris Wilson. I've been working on the web platform a super long time. I started over 26 years ago. I co-wrote the Windows version of NCSA Mosaic, the first real mass market browser after Tim Berners Lee's browser.
[1:10] I've been an engineer, a PM, a lead PM, a GPM, developer advocate. I'm currently on the TPGM team in Chrome. I've worked on four different browsers, I think, and I've been a Googler since 2010. By the way, that's since Chrome version 6. Chrome version 6 shipped a week after I started. Don't take this the wrong way. That sounds super impressive. I don't think I'm the smartest person in the room, certainly not in this room.
[1:43] I have been in the room where it happened, to borrow a Hamilton quote for a second, many, many times over the years, which is pretty cool. But-- so I want you to all cast your minds back, for some of you, before you were born, to 1988. 1988 is when I went to the University of Illinois as an undergraduate. And to give you a picture of the internet at the time, this chart is great. You can't really read the labels, but 1988 it is here, basically. And you'll note it almost doesn't exist.
[2:16] No one had really heard of the internet at that point. In fact, it was still commonly known as ARPANET in academic circles. And my incoming undergraduate class was not issued email accounts by default. You actually had to go to the computer lab, ask for one in-person. And, in fact, we logged into our mainframe. Like, people didn't usually have the ability to connect. And you had a time limit of seven hours a week on this mainframe system.
[2:47] And I would usually burn this up playing Ultimate Larn, because you only had seven hours. I'd usually burn it up in the first couple days, and then I couldn't check my email again till Saturday morning. Thankfully, engineering students got a second account that was not time restricted on a different mainframe. So clearly, I did pass my computer science classes. This was my first internet terminal. It was a cast off terminal from a job that I was working at over the summer. It was an HP 2622A terminal.
[3:20] It had an integrated thermal printer in the top. It was awesome. I connected this to the University of Illinois' system via a smoking fast, for the time, 2,400 baud modem. For reference, I calculated my cell phone gets something like 6,000 times faster connection overall LT, and a 60,000 times faster connection when I'm on Wi-Fi at home. Or it's about twice the speed of my hotel Wi-Fi here in Mountain View.
[3:50] But this was just a text terminal. Like, the internet was mostly text. In fact, that's one of the points I made here is, it really was email, it was was Usenet, it was IRC, it was Gopher. FTP was cool too, but frankly, used a lot less, except for sharing software. Now don't worry. My entire presentation is not just Douglas Adams quotes. There are a couple more, I think. But this is really-- this is something to remember all the time.
[4:21] Anything that's in the world when you're born or when you're very young it's just normal. It's the way the world works. I have two daughters. The internet is the way the world works. They don't even think about it. Mobile devices? Absolutely. Anything that's invented between when you're 15 and 35 is new, exciting, and you can probably get a career in it. And the internet, the web, was definitely invented between when I was 15 and 35. Now, I'm not really here to say, get off my lawn you young whippersnappers.
[4:52] The web's been done. Everything you can come up with is against the natural order of things. The challenge is, really, how do you take it and make it so that you can adapt to the natural order of things. Think of what it can become in the future. Because otherwise, I turned 35 before Chrome was released, so that would be a problem. In 1991, I got a part time job working at the National Center for Supercomputing Applications. It's the last time I'm going to spell that out. The NCSA is one of the five original NSF supercomputing centers, and our group's mission inside NCSA was to build software tools to enable researchers to use the power of the supercomputers on their desktop.
[5:39] So we did Telnet. We literally built Telnet. In fact, that's what I was hired to do, work on the terminal. Now keep in mind, this was before Windows 95. This was before Windows 95. There was no TCP/IP network stack. PC Telnet was DOS software. We had to eventually build Windows software. We also did visualization tools and things like that. Data loading and formatting tools, that kind of thing.
[6:11] But this fit right in when we had this project come up, where a couple guys came up with this X Windows software, called Mosaic, that let you access this thing that some guy in Switzerland had come up with called the worldwide web. Used a prototype document language called HTML. That was kind of-- well, that was the next 26 years my life. I co-wrote the Windows version of this.
[6:42] Incidentally, NCSA Mosaic had three versions, Mac, PC, Windows, and X Windows. They were totally different. They did not share code at all. We looked at each other's code, but cross platform software, not really a thing. I also, this utterly ruined the word mosaic for me. If you say the word mosaic, I will not think of a piece of art. But keep in mind, again, we didn't have network support in Windows. Windows didn't have a built in network driver.
[7:15] Like, they didn't have sockets. You could buy a separate package that would add it. Even Windows 3.11, with networking, I can't remember the toll name. Windows for Work Groups, I think. It didn't have ti TCP/IP built in. Didn't have sockets. It had networking, but through Novell or something else. So we already had our own network stack. We actually literally wrote the device drivers for network cards. Like, I would debug this stuff. I debugged the TCP/IP fallback algorithm at one point.
[7:50] And so we got that working in Windows. We built the HTML parsing and rendering stuff, all that kind of thing. And NCSA had this tradition of shipping lots and lots of beta releases. Like, basically, build it on your machine, put up a release. I think I actually put up several debug version releases, because I couldn't find a bug once that turned out to be a pointer initialization, of course. But we put Windows Mosaic up on the FTP server for the first time.
[8:20] And I remember, we got super excited, because a week later, we were at 1,000 downloads. Now, I gave this talk I think in 2011, and I calculated like, how long it took Firefox to get 1,000 downloads, and it was measured in fractions of a second. So a little different scale. But still, what was really surprising was, the game DOOM came out the same year, and we still managed to get work done on Mosaic, because we were college kids.
[8:53] I mean, we were students. NCSA had this great overall charter of hey, go enable education and research. And we got to explore a lot of things. And if we didn't have that there, we wouldn't have gotten to go build a web browser. It wasn't in our software tool group's charter at the time. We were chartered to build image visualization tools, Telnet, et cetera. And this is one of the things, one of the parallels that I draw with Google, because Google has a lot of that flexibility.
[9:26] It's one thing that I really like about working here. Now, but overall, like, we made a bunch of foolish mistakes in Mosaic, because we didn't really know what we were doing. We didn't really have a whole lot of support. We didn't have a business plan. I mean, plenty of dotcoms didn't have business plans too, but we didn't really, like, there was no user experience class in my computer science degree. There was no theory of software testing or anything like that.
[9:56] And we didn't even have revision control systems. Like, there were two of us working on Windows Mosaic. We didn't have network drives. So literally, we would like, work on the same code, we'd save it to a zip disk, walk across the office, stick it in the other guy's drive, copy the right files, hope for the best. So we did make some foolish choices. And one in particular that I personally own is this. I'm personally responsible for overlapping bold and italic tags working in the early web.
[10:32] For some reason, I thought this would be cool. The rampant violation of all common sense and SGML-structured document decency. And by the way, yes, we do still support this in Chrome and every other browser, probably. We do it in an interesting way that doesn't violate everything that's decent. But in my defense, such as it is, I thought it would be cool at the time. But the early web, even the really early web, because remember, I'm in like, '93 ish year.
[11:10] It was really compelling. And the reason it was compelling was that you got access to all this information. I mean, Google's mission is organize the world's information and make it universally accessible and useful. And I was the one chatting in the back when Parisa asked this question earlier, because it's in my deck a couple times. And you have to remember, at this day and age, the world's information wasn't on the internet. The internet was like, we were off at the low part of that ramp, right?
[11:42] A lot of that information wasn't even in digital form yet. Like, you had to go to a library to get information. Now, eventually, of course, like, anybody who's watched a bunch of information before and knows how we tend to think of the web platform, you'll recognize part of this LICE acronym here. But at this point, it wasn't indexable, really. Or it was indexable, but there were no indices to it. In fact, I meant to bring along, on my bookshelf, I have this book. Like, a bound paper book, that is literally lists of URLs and descriptions of them.
[12:18] It was published, I think, in '93. '93 or '94, I can't remember which. And it's just a solid book filled with, hey, this is what you can find on the Honolulu Community College Website or the like. So most critically, at NCSA we had this-- we recognized that the coolest thing about this web thing was that everyone could be an author, because most of the systems out there weren't really designed for anybody to put servers up and share information.
[12:51] Gopher in particular. Like, Gopher clients were easily accessible. Gopher server software you had to pay an arm and a leg for. Like, basically only universities ran it or private enterprises, because it was so expensive to run the software. Now, so we actually implemented a bunch of stuff at NCSA to try to encourage this sharing of information. We actually had, even in 1993, we implemented a group annotation feature.
[13:21] Like, you could annotate web pages, and then anybody in your group who shared the same annotation server, they would see your annotations when they went to the same web pages. We also had this idea that the web server software should be free, and everyone should run a server on their machine. Now, putting this in context, this was several generations of massive security problems away from where we are today. We actually, I ran a web server on my PC in my office at NCSA.
[13:54] It was world accessible. I mean, literally anybody could just FTP into my personal. In fact, we wrote a networked space dogfighting game. Me and a group of my friends at the University, we borrowed the NCSA PC Telnet code to do this. And after we'd been playing it, like, we got it up and running. It was like, awesome. Those early LAN parties. It was great. After we had it up and running for a while, I realized that I never disabled the FTP server in the PC Telnet code.
[14:26] So sure enough, I could like, FTP into my friends' machine while he was playing the game and, you know, start a big download. He didn't really like that. But the cool thing was there was lots of wacky content. Like, this was groundbreaking at the time, because you didn't have access to this content. Like, there was a guy named Kevin Hughes from the Honolulu Community College who, they have a really cool dinosaur museum at this community college in Honolulu. And so he thought, oh, this is awesome.
[14:58] I'll take some pictures of it with my digital camera and put it online. And he did. And there was like, you would just get this weird kind of stuff. And this is, more than anything, I think what contributed to the growth of the web was this concept of the long tail. Who has not heard of the long tail before? Just to-- OK, so there's a few, which is good. This is where the large portion of content out there-- the overall population is in this tail. And unfortunately, the colors are messed up. But like, all of this stuff out here, measured by interest, is just as popular as the most popular things.
[15:35] So another way to look at this is, the web is incredible, because people get super interested in uncommon topics, more so, even, sometimes, then Taylor Swift's latest video. Which is great, by the way. This is taken for granted today. Like, this is one of those things where you're nodding your head and saying, yeah, whatever. This was new back then, because you couldn't really get access to the long tail, not in the early '90s. In fact, in the early '90s, or mid '90s, actually, in 1996, I took a class learning to play the didgeridoo.
[16:12] Part of the class was how to build one. I was like, oh, this is really cool, and I put up a web page, how to build a bamboo didgeridoo. It's pretty easy, by the way. You just poke a hole in it more or less. But how many of you remember GeoCities? Right on. Nostalgia buffs, I love it. I put up a GeoCities site on how to build didgeridoos from pieces of bamboo, complete with ASCII art, because I didn't own a digital camera yet.
[16:44] This was seven years before Canon came out with the Digital Rebel, just for reference. So it really wasn't that popular, and I put my Microsoft email address on it. And yes, that seems like a crazy thing to do today, but I did. And this page stayed up until GeoCities shut down in 2009. And that entire time, for 13 years, at least once a month, I would get an email from somebody saying, hey, this is great. I was wondering if you know where to get raw bamboo here in Finland.
[17:18] By the way, this page is still accessible. If you really want to see it, the URL is in the speaker notes for this page, but I'm not going to go to it now, because I'm a little ashamed of the artwork there. But I tell this story not because I think you're all interested in building bamboo didgeridoos, although I'm happy to talk about that. Even fewer of you are actually interested in the finer grained details of where to get raw bamboo here in California. I do know, because I did live here for a little while.
[17:49] But you probably have some interests that are just as uncommon. In fact, by contrast, for the last few years, I started making ukuleles in my spare time. And I buy my materials and my tools online. I watch videos on YouTube of how to bend the sides right or that thing. I compare notes on forums about different wood choices, et cetera, browse through exotic woods on eBay. This is a thing. Like, I would search ukulele wood on eBay.
[18:24] And it's not like, five pages. There's like, hundreds of results. And I'm showing my age because I find this amazing. Like, this is blowing, the access to information that you have. This is a massively new natural order. And this leads me to something that I've said for decades about my career, is that the web and the internet just helps human interactions happen faster, and fewer guardrails, fewer speed bumps in the way.
[18:54] I used to think, by the way, this was an unreservedly good thing. I don't think that anymore. So this is kind of foreshadowing, be careful about how you enable human interactions. But it does definitely remove geographic barriers and information barriers. So anyhow, back in 1994, the core Mosaic team all pretty much left NCSA nearly at the same time. Mark Andreessen had left the previous year.
[19:26] I quit and headed out to Seattle to take a different job. And then Mark came back with Jim Clark, scooped up the rest of the engineering team, before they could leave and go off to the winds because they saw that I was the first one that left, but I was not going to be the last. But I went to this company called SPRY. They built a product called Internet in a Box. I literally had one of these on my bookshelf too. Yes, the entire internet in a box.
[19:58] But it was kind of cool, because this was the whole package for what you needed to connect to the internet. Which, again, at the time, was pretty cool. It had a Usenet browser. It had an email system. And had a Gopher client. It also had a web browser. And it still wasn't clear that the web was the winner, by the way. It had all these. Like, when I was building this talk, and I like, you know, did the Command tab on my Mac, and it's like, literally the only things running are two copies of the browser and the calculator.
[20:31] And that's just because it was easier to get to the calculator by clicking the icon. Now, I don't want to talk a whole lot about SPRY in particular, because they went away for good reason. Although it's not Spyglass, by the way. Spyglass was a totally different company. And in fact, a year later I left SPRY and I joined Microsoft and the Internet Explorer team. Spyglass was actually this company that NCSA licensed their code to, because they realized that the business of software licensing was not really the business NCSA wanted to be in.
[21:06] And then Spyglass resold it to everyone else, and Microsoft actually licensed it from spyglass. And Spyglass said they rewrote all the code from the ground up. I'm just saying a lot of that code looked really familiar, and a lot of it, the architectural choices-- yeah, it had some of the same idiosyncrasies as code that I had written. Not that I was proud of, necessarily, but was the same.
[21:38] But I joined the IE team right before we shipped IE 2.0, for context. And I'm sure a few of you have probably heard this quote before. Mark Andreessen was quoted as saying, Netscape will reduce Windows to a set of poorly debugged device drivers. Now, in his defense, by the way, Mark actually said that Bob Metcalf said this, and he was just retweeting it. Well, quoting it, because JavaScript wasn't around.
[22:09] Twitter wasn't around. This may seem like a cheap shot against Microsoft. It actually isn't, because I didn't believe it then. I continued to work for Microsoft for 15 years. I don't even believe it now, because those device drivers are really well debugged at this point. But I don't think any of us expected what this statement kind of foreshadows, that the world is just going to become the web platform, and software sitting on top of it, not a whole bunch of software sitting on top of Windows.
[22:44] And this really did kick off the browser wars. And my favorite example of the hideousness of the browser wars was the blink tag. And how many people have heard the tale of how the blink tag was invented? Wow, OK. So this one was pretty good. I was not in the middle of this one. I was not in the room where this one happened. The blink tag was created because some Netscape engineers went out drinking one night. I'm not kidding. It's on Wikipedia. Look it up.
[23:15] And one of them, or more of them, were like, oh man, we should make a tag that makes everything blink. And they were out drinking, so one of them decides to go back to the office, and the next morning, shows their coworkers the blink tag. Now, at Microsoft, we hated the blank tag. We were like, oh my god, why would you make the-- why would you do this? It's like you're going to, I don't know, trigger people who are sensitive to blinking lights or something.
[23:46] This is horrible. In fact, when the Netscape team demanded that CSS include text decoration blink, I said fine. We'll parse it. We'll apply it, but we can't be forced to make it actually blink. It was in the CSS1 spec, at least. You're not actually required to visually make the thing blink. Now, we still had to out blink them though, and that's what the marquee tag was about. In the marquee tag, just search for marquee tag in Google search.
[24:21] It's actually awesome, because it has now my favorite Easter egg in Google search, because it actually replicates a marquee tag. Like, the tag results start scrolling back and forth. And that's basically what marquee did. It scrolled text back and forth. The joke actually ended up being on us on the IE team, because we also made it scroll vertically and stack text vertically. Like a marquee, you know, when you walk down Times Square or something and there's vertical text.
[24:54] And apparently, this was really popular in Korea, because it matched how their text and fonts worked at the time, and it was useful in developing Korean text. And we literally couldn't remove it for like, decade, more than a decade afterward, because it was so heavily in use and we would have broken a lot of content. Now, in 1996 is when we shipped IE 3, so this is kind of the era we're in.
[25:24] And around this time, it's important to understand, IE, actually, would dynamically lay out pages. Like, if you resize the window, it would just re lay it out. That's actually how I wrote the original rendering layout system in NCSA Mosaic. This is also, by the way, the idiosyncrasy I was talking about earlier, was I would break up runs of text. As you narrowed the window, it would have to break it up at different places, and it-- like, the runs would never recombine. They would just stack.
[25:54] So like, if you stretched it-- if you squeezed the window all the way down, it would take up slightly more memory and have more runs in the overall system. They have the same thing. Now, Netscape Navigator, by the other way, on the other hand, when you resize the window, it would literally reload the page from the network. Not even from disk. Like, disk caching was only going to start being a thing in a year or two.
[26:25] So they would literally go reload the page. And in fact, if you had form fields on the page, and maybe you realized that you couldn't see one of them, and you'd resize the window, it would reload the page and lose everything. They started caching things across page loads for exactly that reason. But we did this kind of feature for feature comparison, but it started being more clear that they had-- they were going for cheaper features than we were.
[27:00] We did do a feature for feature in JavaScript, on tables, on font tags. I am actually the person who implemented CSS first in a browser. This was because my boss actually came into my office and said, hey, we're planning out features for IE 3. We want you to work on frames, because we didn't do frames yet, iframes, frame sets, et cetera. And I was like, hey, that would be cool. But there's this thing called CSS.
[27:30] Netscape's not even looking at this yet. It would be super cool. You can do all this neat visual stuff. And he was like, oh, let me think about it. Came back in 1/2 hour and said, yeah, go do that. And that was how we got CSS in a browser. I mentioned earlier about coding, coding quality, let's say, software systems. And at this point, we did at least have revision control. Like, we had network drives.
[28:01] But in the IE 3 days, our revision control system didn't work so well if multiple people tried to check in at the same time, because we frequently were checking in many different files. And we had what we referred to as the check in bear. This is literally a physical Teddy bear. It sat in a hallway next to a whiteboard. And if you needed to check in, and you had to go get the bear, write your name on the board, take the bear, the bear had to sit on your desk while you were checking in, and then you went back, and if someone else had written their name below yours, you went and gave it to them instead.
[28:36] It was an interesting semaphore, I guess. But after we shipped IE 3, we started looking ahead to IE 4. And at Microsoft, with IE 4, we actually built an entirely new engine, the Trident engine, what became known as the Trident engine. And I found out about this the first time when we were invited to a talk by this group called the Forums Cube Team. No idea what that came from. And there were rumors that they were building something, and I didn't have a chance to go.
[29:10] I was busy doing something. But the other guy who worked on the rendering engine, my friend Jeff, he went. And he comes back. He comes into my office and he's really, really down. I'm like, how did it go? And he's like, we're screwed. They can do everything. They can edit. They can change things. Like, it's a completely live dynamic environment. We're out of a job. And he was half right, because I had done style sheets. And I gave a talk to the Trident team like, a week later, where I was showing off all the stuff I'd done on style sheets.
[29:44] And I was like, does this, does this. I'm hoping to get in these two features before we ship. Now literally, someone in the audience said, could you not, because anything you ship, we have to be compatible with. Now, just for that, it's three features. And so they asked me to move over to the IE 4 team, work on style sheets. And when I was asked to join, that I was told I would be in the object model team. And I'm like, what? The JavaScript team? You asked me to do style sheets. But this was kind of the key thing about this era, was everything became dynamically programmable.
[30:21] Before that, in IE 3, up through IE 3, and still in Netscape Navigator, all you could reprogram were images. Not the size, because you couldn't change the layout, but you could swap the visual out, the links that a particular hyperlink would point to, an input fields. Nothing else. Nothing that changed the layout of the document. And the only way you could change visuals was input fields and images. And suddenly, you could redo everything.
[30:52] I mean, you could change inner HTML and put a whole new document in there. You could change things in the document object model. There were a couple things you couldn't change dynamically. There's a whole 45 plus minute talk about hasLayout here that I'm just going to skip right past, other than to say it really wasn't my fault. People do say that sometimes. It wasn't. And it was super important to understand that Netscape Navigator didn't have a dynamic system. They couldn't change all the stuff dynamically, like, their new system, what became Mozilla, was delayed.
[31:29] To combat this, instead of changing everything live through the object model, they proposed, hey, we should have a new tag called Layer. And you can put things that change inside a layer. But that whole CSS positioning thing, let's not do that. We were like, no, I think we're going to do that. There was a lot of jockeying back and forth. And I think this all culminated when we shipped ActiveDesktop in Windows 98. And this was because you can suddenly drop web content onto the desktop, and all of the window decoration there was actually done in web content.
[32:07] This was horrifying to those of us who really knew what was going on, because it was a very heavy weight system being dropped in to do a very low level system. But this was also when the dawn of Ajax happened, right? This was, Alex Hauptmann, a guy I later worked with in IE, they needed a data transfer system for Outlook Web Access. So they came up with this control, shipped it in MSXML, and this shipped in the IE 5 time frame.
[32:38] I'm not sure which of the IE 5 releases, because literally we had IE 5.0, 5.01, 5.01A, 5.01B, 5.01C, and 5.01D. We were trying to shift together with Office. It took a few tries. And after that, we kind of stumbled at Microsoft. We were largely just re-architecting. Like, IE 5.5 to this native frames thing. And IE 6 fixed all the things we broke in IE 5.5. And that was about it. Really. Like, we didn't really know what to do.
[33:09] And a lot of it is because of this chart. And this is browser adoption, during this time period. And you'll notice there's a nice peak up there, and most people don't do well at peaks. Particularly Microsoft doesn't, but most people don't do well in peaks. But as we shipped IE 6, we were right about here. We had the best browser on the planet. I mean, we were much better than Netscape Navigator in my, admittedly, somewhat biased opinion.
[33:41] Our Mac product was actually better than our Windows product. Or Mac team is applauding somewhere and they don't even know why. But the web didn't actually have rich layout. It did great on flow text. It did great on tables. But it didn't do stacking and it didn't do grids at the time, which was kind of bad. Compatibility was becoming a real problem for us, particularly because Microsoft had this really, really hardcore compatibility philosophy.
[34:12] I remember having to ask for approval to break something to fix our standard support, but it would break something in the Help pages for Microsoft Cart Precision Racing, a game that we had shipped like, three years before that. And overall, like, the web didn't lead developers back to Windows, and Microsoft started questioning, why are we doing all this for something that doesn't get us more developers. And we already have all the users, so why do we need to do this.
[34:45] They just wanted to retain the developer market. So we created this Avalon project, which became dotnet framework 3.0. And I'm not-- there's at least another 45 minute talk in there. And of course, this just ended up in them losing that market too, and then declining it. And of course, at the same time, the world just kept going, right? This pattern of mashup apps became more and more important. I wrote this white paper internally about mashups.
[35:16] And this is basically multiple components and data started coming together. Again, this seems natural today. But the idea that you had the same system that had Chicago crime statistics and mapping software, and that you could just get them to work together dynamically, that was pretty awesome at the time. And, of course, WebKit started gaining traction. Firefox was gaining traction. And the WHATWG was formed around here too, because the W3C kind of lost its way.
[35:46] There are several hours worth of talks there. And in 2004, Microsoft finally woke up, said, oh, wait a second. We need to do something here. And this was actually the release that I was most proud of personally. Not because of what we actually shipped, but because we had to build a team from basically ground zero. And the unfortunate part is, you read-- this is out of the Wikipedia page on IE 7, and it kind of says, new features, including, tab browsing and page zooming, integrated search box, a feed reader.
[36:22] And oh, yeah, web standard support got a little better, but it deal doesn't pass the basic tests. And that-- we had to get used to being vilified at this stage. I did actually have someone in blog comments, posing as Satan, offer me a job at that point. Asked how much I made and if I wanted a job. And I was kind of worried, so I didn't delete the post, because you never know. But don't read the YouTube comments. Don't pay too much attention to people.
[36:53] And I'd point out that, only now are we getting into the period of time where Chrome began. So I'm not actually going to cover any of that, because Peter will do a much better job than I would. But I will say, Microsoft continued to kind of invest the minimum into the platform. Not the browser, but the platform. And that didn't work so well for them. And a lot of this led me to the lessons that I learned out of the IE experience.
[37:23] Don't become complacent just because you're at the top of that heap, and Chrome can definitely learn something there. Don't focus on the competition was a huge part of it. That works OK when there's only two of you, not so well when it's a lot of different people and a lot of things. We're actually pretty good at not doing quirky stuff. We try to pay attention. We try to build lots of test pages and make sure that we're following a spec. But more than anything, not all the smart people work at your company.
[37:55] And, of course, don't ignore disruptive factors like the mobile revolution, which came along right about this time too, right? And this caused us some challenges on Chrome as well. But this was a huge deal, right? Like, I went in 12 years from having this Motorola Startac, which I promise you was super sexy when it came out. It was the best phone out there. I loved that phone. Right up until the point it dropped it into Lake Washington, to having an iPhone. Right? And the iPhone, it had all these sensors, and the touch screen was super engaging, and just so much power in it.
[38:32] And, by the way, I was over 35 when the iPhone was released. But I still managed to adapt, because I remember saying two years later, yeah, baseline. My cell phone has to take the place of my guitar tuner now. Like, it just has to work. I'm not carrying a guitar tuner around anymore. I had a guitar in my office, and I'm pitch sensitive enough that I wanted it to work. And unfortunately, the web wasn't just the mobile platform at that point. It would have been great, but frankly, at that stage, the web was still designed for 1,024 by 768.
[39:07] Literally, it was hard coded in web pages. When Apple came up with their somewhat wacky rules about how to remap onto their device, they were depending on this. And they weren't wrong, really, to make most pages look correct. But it wasn't really open to doing touch input. Occasionally you needed a keyboard, and the network was still pretty spotty. Like, people weren't expecting this. And it's super important. This is actually from around that time period too.
[39:39] Ben Galbraith, well before he worked at Google, he said this at a conference. And he said, web 2.0 isn't about a set of technologies. It's about caring about your user experience, and this was the big evolution then, was people started really caring about their experiences offered in a browser. And prior to that, they really weren't. Post that, we actually had yet another version of that when we had to bring out the Progressive Web App banner a couple of years ago, where we really had to focus on the fact that bandwidth was still required.
[40:15] Like, it didn't-- the web didn't work well if you didn't know you had a connection. And I've given many talks about that. But at this point, the things that I want everyone to focus on is, a big reason that I'm convinced the web platform is still that universal platform, is that those access to capabilities is catching up. We just have to be super careful about security and privacy and the user experience. And, more than anything, how that platform works on other devices.
[40:46] This is also one of the traps that Microsoft fell in. Because even when Microsoft had two browser teams, a Mac team and a Windows team, the Mac team was off in a corner by themselves. They weren't integrated. They weren't thinking about it. And, like I co-chair of the immersive web working group. We have to think about Magic Leap's AR Headset and how WebXR works on it, even though Google is, not currently to my knowledge, building an AR headset. So it's kind of important. Guidance for that, really, this is Google 101, right?
[41:22] Respect the user, respect the platform, respect the community. Don't be the smartest person in the room. For any of you working in standard stuff, be the best listener. That's a much better way to take that on. As Parisa mentioned earlier today, this is our mission on the Chrome team. And this, by the way, overall, this is what brought me to Google. Like, this is a strong part of Google's DNA. It's a strong part of the Chrome team's DNA. This is exactly why I stay here as well.
[41:54] And with that, I think I'm going to close with my final two Douglas Adams quotes. Thank you. [MUSIC PLAYING]
在Vidleaf工作台中打开
搜索转录文本，选择行，复制带时间戳的引文，翻译。
署名
《Web 的历史（Chrome University 2019）》由 Chrome for Developers（https://www.youtube.com/@chromedevs）创作，依据 CC BY 3.0（https://creativecommons.org/licenses/by/3.0/）许可。源视频：https://www.youtube.com/watch?v=kNzoswFIU9M。本页是该视频的文本转录，添加了段落分隔和时间戳；创作者与 Vidleaf 无关联，也不为其背书。Vidleaf 添加了 AI 标点和 AI 生成的摘要；原始措辞仍可在本页查看。
您是创作者或权利持有人吗？请求更正或移除：copyright@vidleaf.app（参见关于这些页面）。
最后更新于