{"id":17177869,"url":"https://github.com/sideshowbarker/web-history","last_synced_at":"2026-03-18T23:52:01.854Z","repository":{"id":12899603,"uuid":"15576644","full_name":"sideshowbarker/web-history","owner":"sideshowbarker","description":"Resources related to the history of the Web","archived":false,"fork":false,"pushed_at":"2014-02-20T07:17:57.000Z","size":736,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-03-20T05:30:41.506Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/sideshowbarker.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-01-02T05:33:04.000Z","updated_at":"2024-08-07T17:01:04.000Z","dependencies_parsed_at":"2022-08-28T14:20:10.910Z","dependency_job_id":null,"html_url":"https://github.com/sideshowbarker/web-history","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sideshowbarker%2Fweb-history","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sideshowbarker%2Fweb-history/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sideshowbarker%2Fweb-history/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sideshowbarker%2Fweb-history/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/sideshowbarker","download_url":"https://codeload.github.com/sideshowbarker/web-history/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245359255,"owners_count":20602322,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-15T00:05:21.891Z","updated_at":"2026-01-06T03:39:39.711Z","avatar_url":"https://github.com/sideshowbarker.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# A brief history of the modern Web Platform\n\n## 2004-02\n\n- [CSS 2.1 Candidate Recommendation (CR)](http://www.w3.org/TR/2004/CR-CSS21-20040225/)\n  published; the spec will later go back to normal Working Draft status for\n  a time and then return again to CR in July 2007 before finally being\n  published in June 2011 as a full W3C Recommendation.\n\n- [Safari 1.2](http://weblogs.mozillazine.org/hyatt/archives/2004_02.html#004874)\n  released; notable in that it's the first version of Safari with\n  XMLHttpRequest (XHR) support (following Internet Explorer and Firefox).\n\n- [Flickr launched](http://en.wikipedia.org/wiki/Flickr); making\n  innovative use of XHR and client-side browser technologies to drive its\n  user interface, adding\n  [\"tagging\" features inspired by del.icio.us](http://en.wikipedia.org/wiki/Tag_%28metadata%29#History),\n  and eventually moving to provide APIs to expose Flickr for data using in\n  other sites and Web applications, it will go on to be often cited as a\n  key example of a\n  [\"Web 2.0\"](http://en.wikipedia.org/wiki/Web_2.0)\n  site/service.\n\n- [Gmail launched](http://en.wikipedia.org/wiki/Gmail),\n  in invitation-only beta, and\n  [Facebook launched](http://en.wikipedia.org/wiki/Timeline_of_Facebook#2004),\n  with membership initially restricted to students of Harvard University.\n\n## 2004-04\n\n- [Web Applications 1.0 first public draft published](http://www.hixie.ch/specs/html/apps/web-apps-1)\n  by Ian Hickson (the document will eventually form the basis for the HTML5\n  spec).\n\n  The publication of the Web Applications 1.0 first draft follows a couple\n  of blog postings from Ian Hickson earlier in the year,\n  [Ramblings from the North](http://ln.hixie.ch/?start=1080506019\u0026count=1)\n  and\n  [Void filling: Web Applications Language](http://ln.hixie.ch/?start=1074466808\u0026count=1),\n  in which Hickson writes:\n\n  \u003e About 11 months ago, I mentioned that the W3C had so far failed to\n  \u003e address a need in the Web community: There is no language for Web\n  \u003e applications[...] I've been taking the opportunity to work on a\n  \u003e proposal for a Web Applications specification[...] something along the\n  \u003e same lines as Web Forms 2, but specifically for client-side application\n  \u003e development.\n\n  In the following month, Hickson writes a related\n  [Backwards Compatibility](http://ln.hixie.ch/?start=1085764602\u0026count=1)\n  blog posting in which is gives some more detail about the rationale\n  behind the Web Applications 1.0 spec:\n\n  \u003e Authors still want to write Web applications, and the currently\n  \u003e deployed standards are inadequate. Since completely new standards won't\n  \u003e cut it [...] this leaves us with the solution we (Opera and Mozilla)\n  \u003e have been advocating: updating HTML and the DOM.\n\n## 2004-06\n\n- [WHATWG launched](http://www.whatwg.org/news/start); announcement:\n\n  \u003e The group aims to develop specifications based on HTML and related\n  \u003e technologies to ease the deployment of interoperable Web Applications\n  \u003e [...] for implementation in mass-market Web browsers, in particular\n  \u003e Safari, Mozilla, and Opera; [the group] intends to ensure that all its\n  \u003e specifications address backwards compatibility concerns [...] and\n  \u003e specify error handling behavior to ensure interoperability even in the\n  \u003e face of documents that do not comply to the letter of the\n  \u003e specifications.\n\n  The announcement of the launch of the WHATWG follows just after a\n  [W3C Workshop on Web Applications and Compound Documents](http://www.w3.org/2004/04/webapps-cdf-ws/)\n  held at Adobe offices in San Jose. For the workshop, Opera and Mozilla\n  jointly submit and present a position paper with a set of proposed\n  [Design Principles for Web Application Technologies](http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html);\n  but some\n  [subsequent blog postings](http://www.w3.org/html/wg/wiki/2004WebAppsWorkshop/reactions)\n  from Brendan Eich, David Baron, and Ian Hickson make it clear that they've\n  come away from the workshop with a realization that their goals with respect\n  to Web applications are not in sync with others in attendance. Brendan Eich:\n\n  \u003e The dream of a new web, based on XHTML+SVG+SMIL+XForms, is just that --\n  \u003e a dream. It won't come true no matter how many toy implementations\n  \u003e there are[...] The best way to help the Web is to incrementally improve\n  \u003e the existing web standards, with compatibility shims provided for IE,\n  \u003e so that web content authors can actually deploy new formats\n  \u003e interoperably[...] Mozilla is joining with Opera and others to explore\n  \u003e the sort of incremental improvements to HTML proposed by us at the\n  \u003e workshop.\n\n## 2004-07 to 2004-12\n\n- [HTML `canvas` element created by the Safari team at Apple](http://ln.hixie.ch/?start=1089635050\u0026count=1)\n  and\n  [first specified as part of Web Applications 1.0](http://web.archive.org/web/20041009144718/http://whatwg.org/specs/web-apps/current-work/).\n\n- [The possibility of an \"HTML 5.0 specification\" is mentioned](http://lists.w3.org/Archives/Public/public-whatwg-archive/2004Aug/0345.html)\n  in a message from Anne van Kesteren on the WHATWG mailing list; and in a\n  [later reply on the same list](http://lists.w3.org/Archives/Public/public-whatwg-archive/2004Nov/0030.html),\n  Ian Hickson says that \"at this point Web Apps [Web Applications 1.0] is\n  basically HTML5\"; subsequently, the term *HTML5* begins to be used in\n  WHATWG discussions as a shorthand name for the Web Applications 1.0 spec.\n\n- [Ruby on Rails first released](http://en.wikipedia.org/wiki/Ruby_on_Rails#History)\n  by David Heinemeier Hansson. Among other things, it becomes notable as\n  one of the first server-side Web-application development frameworks that\n  provide specific support for XHR-driven Web applications (what will in\n  2005 start to referred to as \"Ajax\" applications).\n\n- [Opera begins to ship pre-installed on some mobile devices](http://www.kddi.com/english/corporate/news_release/2004/1006/),\n  becoming -- three years before the release of iPhone and mobile Safari --\n  the first \"full\" mobile browser (non-WAP, JavaScript-enabled, using the\n  same browser engine as desktop Opera) to generate any significant mobile\n  browsing traffic to normal (non-WAP) websites (though the usage largely\n  comes just from mobile phones in Japan, which at that time are still\n  significantly more advanced than mobile devices elsewhere in the world).\n\n- [Web 2.0 Conference](http://web.archive.org/web/20041001091530/www.web2con.com/pub/w/32/program.html)\n  takes place in San Francisco, eventually causing the term *Web 2.0* to be\n  brought into general use.\n\n## 2005-02\n\n- [Google Maps launched](http://en.wikipedia.org/wiki/Google_maps#History)\n  in beta with support across all major browsers (Internet Explorer, Mozilla,\n  Opera, and Safari), following just after the launch, two months earlier, of\n  [Google Suggest](http://googleblog.blogspot.com/2004/12/ive-got-suggestion.html)\n  as a Google \"Labs\" project.\n\n- [Ajax: A New Approach to Web Applications](http://www.adaptivepath.com/ideas/essays/archives/000385.php)\n  by Jesse James Garrett; coining the term *Ajax* to describe XHR-driven\n  modern Web applications, Garrett specifically mentions JSON as a \"means\n  of structuring data for interchange\" in such applications, and cites\n  Gmail, Google Suggest, Google Maps, and Flickr as examples.\n\n- [Prototype JavaScript Framework created](http://en.wikipedia.org/wiki/Prototype_JavaScript_Framework)\n  by Sam Stephenson; included with Ruby on Rails, it's one of the first\n  JavaScript libraries to include specific mechanisms for building\n  XHR-driven applications.\n\n## 2005-03 to 2005-06\n\n- [Cross-document messaging (`postMessage`)](http://web.archive.org/web/20050301091946/http://whatwg.org/specs/web-apps/current-work/)\n  first specified, as part of Web Applications 1.0.\n\n- [CouchDB created](http://en.wikipedia.org/wiki/CouchDB#History)\n  by Damien Katz; it's notable in being intended as a \"database that\n  completely embraces the web\" -- using JSON, JavaScript, and HTTP, and\n  fundamentally designed for serving Web applications. (More specifically,\n  it's schema-less and non-relational, storing data as JSON-formatted\n  semi-structured documents, built on a non-SQL, JavaScript-based query\n  mechanism -- with a MapReduce-driven view model -- and with a RESTful\n  HTTP API for consuming and exposing data in JSON (PUT/POST data as JSON\n  objects, and GET results as JSON objects).\n\n- [Acid2](http://en.wikipedia.org/wiki/Acid2) published by Ian Hickson as a\n  means to test the level of standards conformance in Web browsers.\n\n- [Opera 8](http://en.wikipedia.org/wiki/History_of_the_Opera_web_browser#Version_8)\n  released; notable in that it's the first release version of Opera with\n  (limited) XHR support, which finally makes XHR available across all major\n  browser engines.\n\n- [The Web Platform - Browsers and Applications](http://www.w3.org/2005/Talks/0513-webplatform/)\n  talk presented by Dean Jackson in the W3C track at WWW2005, with the\n  goals of the \"Web Platform\" outlined as:\n\n  * To (better) enable the Web as an application platform (on all devices)\n  * To help users by requiring support for standards in the browser.\n  * To give Web developers a better programming environment (with new\n    interfaces).\n\n  Going forward, the term \"the Web Platform\" will come into increasing use\n  specifically for describing the standard set of client-side technologies\n  made available in browsers, for building modern Web applications.\n\n- [script.aculo.us created](http://en.wikipedia.org/wiki/Script.aculo.us)\n  by Thomas Fuchs; built on top of the Prototype JavaScript Framework and\n  included in Ruby on Rails, it's one of the first \"Ajax\" script libraries\n  to come into wide use.\n\n## 2005-07 to 2005-11\n\n- [`\u003c!DOCTYPE html\u003e` (HTML5 doctype) first introduced](http://web.archive.org/web/20050701075402/http://www.whatwg.org/specs/web-apps/current-work/).\n\n- [Client-side local storage](http://www.whatwg.org/specs/web-apps/2005-09-01/)\n  first specified, as part of Web Applications 1.0.\n\n- [del.icio.us begins providing a RESTful HTTP API that makes data available in JSON](http://inkdroid.org/journal/2005/09/21/delicious-json/);\n  within the next three years, Flickr, Yahoo, Google, and most other major\n  providers of Web-based services begin to provide similar HTTP APIs that\n  expose data formatted in JSON.\n\n- [What Is Web 2.0](http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html)\n  article by Tim O'Reilly. Subsequent discussions of the term *Web 2.0*\n  often cite this article; excerpt:\n\n  \u003e It's clear that standards and solutions [...] will enable the next\n  \u003e generation of applications. [...] AJAX is also a key component of Web\n  \u003e 2.0 applications such as Flickr[...] We're entering an unprecedented\n  \u003e period of user interface innovation, as web developers are finally able\n  \u003e to build web applications as rich as local PC-based applications.\n\n- [Web API](http://www.w3.org/2006/webapi/) and\n  [Web Application Formats](http://www.w3.org/2006/appformats/)\n  Working Groups chartered at the launch of the W3C\n  [Rich Web Client Activity](http://www.w3.org/News/2005#x200501115c).\n\n  The Web API Working Group mission is described as being to \"enable\n  improved client-side application development on the Web\" and its a scope\n  includes, among other things, documenting the Window and XMLHttpRequest\n  (XHR) interfaces and the `setTimeout` method, as well as specifying\n  \"network communication methods\" and a means for \"persistent storage on\n  the client\" to facilitate \"more advanced Web applications, enabling them\n  to store user preferences and possibly work in an offline environment,\n  such as a laptop or mobile phone with intermittent connectivity\".\n\n## 2006-01 to 2006-02\n\n- [Firebug](https://addons.mozilla.org/en-US/firefox/addon/firebug/versions/?page=5#version-0.2)\n  first version released by Joe Hewitt.\n\n- [Opera Mini](http://en.wikipedia.org/wiki/Opera_Mini)\n  released; it will play a role in expanding Web access to more parts of\n  the world, and will end up consistently accounting for a significant\n  percentage of worldwide mobile Web-browsing traffic.\n\n- [JSON Internet Draft published](http://ietfreport.isoc.org/all-ids/draft-crockford-jsonorg-json-00.txt)\n  by Doug Crockford; however, it\n  [had already been documented by Crockford elsewhere](https://web.archive.org/web/20030417010540/http://www.crockford.com/JSON/)\n  going back to at least late 2002, and a number of major Web-based\n  services had already started to provide APIs that exposed data formatted\n  in JSON.\n\n- [HTML parsing algorithm](http://web.archive.org/web/20060202011253/http://whatwg.org/specs/web-apps/current-work/)\n  first specified, as part of Web Applications 1.0.\n\n## 2006-07 to 2006-11\n\n- [Twitter first launched](http://techcrunch.com/2006/07/15/is-twttr-interesting/)\n  and\n  [Facebook first opened widely](http://en.wikipedia.org/wiki/Timeline_of_Facebook#2006)\n  for all users to join.\n\n- [jQuery 1.0](http://blog.jquery.com/2006/08/26/jquery-10/) released.\n\n- [Internet Explorer version 7](http://en.wikipedia.org/wiki/Internet_Explorer#Version_7)\n  released with CSS and DOM improvements -- five years after the release of IE6.\n\n- [Reinventing HTML](http://dig.csail.mit.edu/breadcrumbs/node/166)\n  posting by Tim Berners-Lee:\n\n  \u003e Some things are clearer with hindsight of several years. It is\n  \u003e necessary to evolve HTML incrementally. The attempt to get the world to\n  \u003e switch to XML, including quotes around attribute values and slashes in\n  \u003e empty tags and namespaces all at once didn't work[...] The plan is to\n  \u003e charter a completely new HTML group. Unlike the previous one, this one\n  \u003e will be chartered to do incremental improvements to HTML, as also in\n  \u003e parallel xHTML.\n\n- [Proposed charter](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0045.html)\n  for HTML Working group posted by Ian Hickson (following\n  [the earlier posting of shorter proposed charter](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0000.html),\n  [specific feedback](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0000.html)\n  and some\n  [public discussion about charter review](http://lists.w3.org/Archives/Public/www-archive/2006Nov/thread.html#msg53)).\n\n## 2007-03 to 2007-05\n\n- [Fifth W3C HTML Working Group](http://www.w3.org/2007/03/HTML-WG-charter.html)\n  chartered (though only the second W3C HTML working group to focus on the core\n  HTML language), with a mission *to continue the evolution of HTML (including\n  classic HTML and XML syntaxes)* and with a statement that *this group\n  will maintain and produce incremental revisions to the HTML specification [to\n  produce] a language evolved from HTML4 for describing the semantics of\n  documents and applications on the World Wide Web.*\n\n- [`video` and `audio` elements added to the HTML spec](http://html5.org/r/394-699).\n\n- [Google Gears](http://gearsblog.blogspot.com/2007/05/posted-by-aaron-boodman-and-erik.html)\n  released; some of its key features, such as its \"workerpool\" mechanism,\n  eventually become standard parts of the Web platform, and by the end of\n  2009 its development will end up being permanently halted.\n\n## 2007-06 to 2007-12\n\n- [iPhone](http://en.wikipedia.org/wiki/History_of_the_iPhone#World_timeline)\n  first released; notable among other things in that it doesn't include\n  support for Adobe Flash, it will end up consistently accounting for\n  significantly more mobile Web-browsing traffic than any other mobile\n  device.\n\n- [HTML \"offline Web applications\" feature introduced](http://html5.org/tools/web-apps-tracker?from=848\u0026to=1115)\n  (`applicationCache` interface, _aka_ appCache)\n\n- [CSS Transforms](https://www.webkit.org/blog/130/css-transforms/) \n  and\n  [CSS Transitions](https://www.webkit.org/blog/138/css-animation/)\n  (`transform-*` and `transition-*` properties) created by the Safari team at Apple.\n\n- [Downloadable-fonts support added to WebKit](https://www.webkit.org/blog/124/downloadable-fonts/);\n  (`@font-face` rule). Eventually, by mid-2009, downloadable fonts will be\n  supported in all major browsers. (Note that Internet Explorer was the\n  first to have downloadable-fonts support, starting with the release of\n  IE4 in 1997 -- and the feature had actually been part of the CSS2.0\n  Recommendation published in 1998.)\n\n- [Futhark JavaScript engine released in beta](http://my.opera.com/desktopteam/blog/2007/10/25/opera-9-5-beta-released)\n  as part of Opera 9.5; for a time it will be the fastest JavaScript engine\n  on the market, and help to initiate a JavaScript-engine performance race\n  among browser projects, starting in mid-2008.\n\n- [Android mobile-device platform announced](http://www.openhandsetalliance.com/press_110507.html);\n  it is notable for including a mobile browser that uses WebKit as its\n  browser engine; however, it will be nearly a year before any Android\n  devices actually begin to ship.\n\n- [SunSpider JavaScript benchmark introduced](https://www.webkit.org/blog/152/announcing-sunspider-09/)\n  by the Safari team at Apple; during the latter half of 2008 and after, it\n  will become widely used by other major browser projects in documenting\n  the relative performance improvements in their JavaScript engines.\n\n## 2008-01 to 2008-06\n\n- [First W3C Working Draft of HTML5 published](http://www.w3.org/News/2008.html#entry-6935).\n\n- [Acid3](http://en.wikipedia.org/wiki/Acid3)\n  published by Ian Hickson as a means to test the level of standards\n  conformance in Web browsers.\n\n- [GitHub launched](https://github.com/blog/40-we-launched).\n\n- [SquirrelFish JavaScript engine announced](https://www.webkit.org/blog/189/announcing-squirrelfish/)\n  by the Safari team at Apple; it's an incremental rewrite of Safari's\n  \"JavaScriptCore\" engine to turn it into a bytecode interpreter, resulting\n  in large performance improvements.\n\n  During the following months, other browser projects begin to rewrite\n  their JavaScript engines in a race that over the following next few years\n  eventually results in vastly improved overall speed of JavaScript\n  execution across all major browsers.\n\n- [W3C Web Applications Working Group launched](http://www.w3.org/blog/news/archives/286);\n  the group merges the existing Web APIs Working Group and Web Application\n  Formats Working Group into a single group, with a mission to *provide\n  specifications that enable improved client-side application development\n  on the Web*\n\n- [Geolocation API first Editor's Draft written and announced](http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0000.html)\n  by Andrei Popescu.\n\n## 2008-07 to 2008-10\n\n- [Web Sockets and Web Workers first specified](http://html5.org/tools/web-apps-tracker?from=1835\u0026to=1968).\n\n- [Geolocation API ships in Google Gears 0.4](http://gearsblog.blogspot.jp/2008/08/gears-04-is-here.html),\n  the first implementation of the Geolocation API to be made available.\n\n- [Firefox developer builds begin shipping with TraceMonkey](http://news.cnet.com/8301-1001_3-10023723-92.html),\n  a JIT-based JavaScript engine (compiling JavaScript to native machine\n  code) that provides greatly improved JavaScript performance.\n\n- [Google Chrome first released](http://googleblog.blogspot.jp/2008/09/google-chrome-now-live.html),\n  with WebKit as its browser engine, and notable for being the first\n  release version of a browser to ship with a JIT-based JavaScript engine,\n  V8, which provides greatly improved JavaScript performance on par with\n  Mozilla's TraceMonkey (which had been released to developers less that a\n  month earlier).\n\n- [WebKit announces SquirrelFish Extreme](https://www.webkit.org/blog/214/introducing-squirrelfish-extreme/),\n  a new JIT-based JavaScript engine with performance on par with V8 and\n  TraceMonkey.\n\n  Over the coming months, the browser projects will all race with each\n  other further to incrementally improve the performance of their\n  JavaScript engines, with the result over the long term being a vast\n  improvement in the overall speed of JavaScript execution across all major\n  browsers -- which among other things ends up enabling browsers to behave\n  performantly with JavaScript-heavy Web application even on mobile devices\n  with relatively limited RAM and CPU resources.\n\n- [First Android device ships](http://en.wikipedia.org/wiki/HTC_Dream#History):\n  the HTC dream, running Android 1.6; notable in that it's the first\n  non-iPhone smartphone to ship with a WebKit-based browser. Other\n  Android-based mobile devices will begin to ship in 2009, resulting in\n  Android devices accounting for a significant percentage of\n  mobile-browsing traffic by the end of 2010, when Android becomes the\n  most widely used smartphone platform worldwide.\n\n- [Geolocation API ships in Firefox 3.1 beta](http://arstechnica.com/information-technology/2008/10/first-look-firefox-3-1-beta-1-officially-released/).\n\n## 2009-02 to 2009-06\n\n- [CSS Animations created by the Safari team at Apple](https://www.webkit.org/blog/324/css-animation-2/)\n  (`@keyframes` rule and `animation-*` properties).\n\n- [Internet Explorer version 8](http://en.wikipedia.org/wiki/Internet_Explorer#Windows_Internet_Explorer_8)\n  released; it is the first version of IE to pass [Acid2](http://en.wikipedia.org/wiki/Acid2).\n\n- [Node.js first released](https://github.com/joyent/node/commit/80eed19612db0fe54191683e8a9f0bc5c1ca4ff6)\n  by Ryan Dahl; it's a software platform notable for being built around the\n  V8 JavaScript engine -- providing a way for developers to do server-side\n  development in JavaScript using a non-threaded, non-blocking \"evented\n  I/O\"-based, asynchronous callback-driven programming model similar to the\n  client-side event-loop-based programming model provided by Web browsers.\n\n- [Geolocation API support ships in i0S 3.0](http://radar.oreilly.com/2009/06/geolocating-your-iphone-users.html),\n  making the iPhone the first mobile device with native support for the\n  Geolocation API in its browser. (Support for Android devices will ship a\n  few months later, in Android 2.0).\n\n## 2009-09\n\n- [WebGL support lands in Firefox Nightly](https://hacks.mozilla.org/2009/09/webgl-for-firefox/)\n  and, shortly after, also\n  [lands in WebKit nightlies](https://www.webkit.org/blog/603/webgl-now-available-in-webkit-nightlies/)\n  and [Chrome developer builds](https://groups.google.com/d/msg/chromium-dev/DusnVs_TGGA/Z9p_p3joTy4J)\n  -- thought the WebGL specification\n  [isn't actually published until December 2009](http://www.khronos.org/webgl/public-mailing-list/archives/0912/msg00000.html).\n\n## 2010-02\n\n- [Google Gears development officially stopped](http://gearsblog.blogspot.com/2010/02/hello-html5.html)\n  by the Gears team at Google, following a gradual shift \"towards bringing\n  all of the Gears capabilities into web standards like HTML5\".\n\n## 2010-04\n\n- [Steve Jobs \"Thoughts on Flash\"](http://www.apple.com/hotnews/thoughts-on-flash/);\n  excerpt:\n\n  \u003e [...] the mobile era is about low power devices, touch interfaces and\n  \u003e open web standards – all areas where Flash falls short[‥.] Rather than\n  \u003e use Flash, Apple has adopted HTML5, CSS and JavaScript – all open\n  \u003e standards[...] Perhaps Adobe should focus more on creating great HTML5\n  \u003e tools for the future, and less on criticizing Apple for leaving the\n  \u003e past behind.\n\n## 2011-03\n\n- [Internet Explorer version 9](http://en.wikipedia.org/wiki/Internet_Explorer_9)\n  released, with major improvements in standards support (including support\n  for the Geolocation API, SVG and the HTML `canvas` and `video` elements).\n\n- [Video conferencing and peer-to-peer communication](http://html5.org/tools/web-apps-tracker?from=5944\u0026to=5945)\n  section added to the WHATWG HTML spec by Ian Hickson.\n\n  [Announced on the WHATWG mailing list](http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Mar/0238.html),\n  this new section of the HTML spec introduces the `getUserMedia` method,\n  `PeerConnection` interface, and `MediaStream` interface (initially just\n  named `Stream`). The content of the section will eventually be forked\n  by the W3C WebRTC Working Group to create the\n  [WebRTC spec](http://dev.w3.org/2011/webrtc/editor/webrtc.html), but even\n  at this point in 2011 when it is first introduced, it already provides\n  for all of the following:\n\n  \u003e Getting a multimedia stream (video, audio, or both) from local devices\n  \u003e (video cameras, microphones, Web cams) or from prerecorded files\n  \u003e provided by the user; Recording such streams locally; Connecting to\n  \u003e remote peers using NAT-traversal technologies such as ICE, STUN, and\n  \u003e TURN; Sending the locally-produced streams to remote peers and\n  \u003e receiving streams from remote peers; Displaying such streams (both the\n  \u003e locally-produced ones and the remotely-obtained ones) locally using the\n  \u003e video or audio elements; Sending arbitrary data to remote peers.\n\n## 2011-11\n\n- [Flash Player for mobile devices end-of-lifed by Adobe](http://blogs.adobe.com/conversations/2011/11/flash-focus.html);\n  the news is widely interpreted as a major shift by Adobe toward HTML5 and\n  away from Flash; excerpt from the announcement:\n\n  \u003e HTML5 is now universally supported on major mobile devices, in some\n  \u003e cases exclusively. This makes HTML5 the best solution for creating and\n  \u003e deploying content in the browser across mobile platforms.\n\n## 2012-02\n\n- [Adobe reduces Flash roadmap to just two areas: gaming and premium video](http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html);\n  the news is widely interpreted as a further focusing by Adobe away from\n  Flash and toward HTML5 and other \"modern web technologies\":\n\n  \u003e With the growth of competition in the browser market, browser vendors\n  \u003e are increasingly innovating and providing functionality that makes it\n  \u003e possible to deploy rich motion graphics directly via browser\n  \u003e technologies, a role once served primarily by Flash Player.\n  \u003e Increasingly, rich motion graphics are being deployed directly via the\n  \u003e browser using HTML5, CSS3, JavaScript and other modern web\n  \u003e technologies. Adobe expects that this trend will continue and\n  \u003e accelerate, and Adobe will continue to play an active role in this\n  \u003e space.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsideshowbarker%2Fweb-history","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsideshowbarker%2Fweb-history","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsideshowbarker%2Fweb-history/lists"}