├── LICENSE └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # A brief history of the modern Web Platform 2 | 3 | ## 2004-02 4 | 5 | - [CSS 2.1 Candidate Recommendation (CR)](http://www.w3.org/TR/2004/CR-CSS21-20040225/) 6 | published; the spec will later go back to normal Working Draft status for 7 | a time and then return again to CR in July 2007 before finally being 8 | published in June 2011 as a full W3C Recommendation. 9 | 10 | - [Safari 1.2](http://weblogs.mozillazine.org/hyatt/archives/2004_02.html#004874) 11 | released; notable in that it's the first version of Safari with 12 | XMLHttpRequest (XHR) support (following Internet Explorer and Firefox). 13 | 14 | - [Flickr launched](http://en.wikipedia.org/wiki/Flickr); making 15 | innovative use of XHR and client-side browser technologies to drive its 16 | user interface, adding 17 | ["tagging" features inspired by del.icio.us](http://en.wikipedia.org/wiki/Tag_%28metadata%29#History), 18 | and eventually moving to provide APIs to expose Flickr for data using in 19 | other sites and Web applications, it will go on to be often cited as a 20 | key example of a 21 | ["Web 2.0"](http://en.wikipedia.org/wiki/Web_2.0) 22 | site/service. 23 | 24 | - [Gmail launched](http://en.wikipedia.org/wiki/Gmail), 25 | in invitation-only beta, and 26 | [Facebook launched](http://en.wikipedia.org/wiki/Timeline_of_Facebook#2004), 27 | with membership initially restricted to students of Harvard University. 28 | 29 | ## 2004-04 30 | 31 | - [Web Applications 1.0 first public draft published](http://www.hixie.ch/specs/html/apps/web-apps-1) 32 | by Ian Hickson (the document will eventually form the basis for the HTML5 33 | spec). 34 | 35 | The publication of the Web Applications 1.0 first draft follows a couple 36 | of blog postings from Ian Hickson earlier in the year, 37 | [Ramblings from the North](http://ln.hixie.ch/?start=1080506019&count=1) 38 | and 39 | [Void filling: Web Applications Language](http://ln.hixie.ch/?start=1074466808&count=1), 40 | in which Hickson writes: 41 | 42 | > About 11 months ago, I mentioned that the W3C had so far failed to 43 | > address a need in the Web community: There is no language for Web 44 | > applications[...] I've been taking the opportunity to work on a 45 | > proposal for a Web Applications specification[...] something along the 46 | > same lines as Web Forms 2, but specifically for client-side application 47 | > development. 48 | 49 | In the following month, Hickson writes a related 50 | [Backwards Compatibility](http://ln.hixie.ch/?start=1085764602&count=1) 51 | blog posting in which is gives some more detail about the rationale 52 | behind the Web Applications 1.0 spec: 53 | 54 | > Authors still want to write Web applications, and the currently 55 | > deployed standards are inadequate. Since completely new standards won't 56 | > cut it [...] this leaves us with the solution we (Opera and Mozilla) 57 | > have been advocating: updating HTML and the DOM. 58 | 59 | ## 2004-06 60 | 61 | - [WHATWG launched](http://www.whatwg.org/news/start); announcement: 62 | 63 | > The group aims to develop specifications based on HTML and related 64 | > technologies to ease the deployment of interoperable Web Applications 65 | > [...] for implementation in mass-market Web browsers, in particular 66 | > Safari, Mozilla, and Opera; [the group] intends to ensure that all its 67 | > specifications address backwards compatibility concerns [...] and 68 | > specify error handling behavior to ensure interoperability even in the 69 | > face of documents that do not comply to the letter of the 70 | > specifications. 71 | 72 | The announcement of the launch of the WHATWG follows just after a 73 | [W3C Workshop on Web Applications and Compound Documents](http://www.w3.org/2004/04/webapps-cdf-ws/) 74 | held at Adobe offices in San Jose. For the workshop, Opera and Mozilla 75 | jointly submit and present a position paper with a set of proposed 76 | [Design Principles for Web Application Technologies](http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html); 77 | but some 78 | [subsequent blog postings](http://www.w3.org/html/wg/wiki/2004WebAppsWorkshop/reactions) 79 | from Brendan Eich, David Baron, and Ian Hickson make it clear that they've 80 | come away from the workshop with a realization that their goals with respect 81 | to Web applications are not in sync with others in attendance. Brendan Eich: 82 | 83 | > The dream of a new web, based on XHTML+SVG+SMIL+XForms, is just that -- 84 | > a dream. It won't come true no matter how many toy implementations 85 | > there are[...] The best way to help the Web is to incrementally improve 86 | > the existing web standards, with compatibility shims provided for IE, 87 | > so that web content authors can actually deploy new formats 88 | > interoperably[...] Mozilla is joining with Opera and others to explore 89 | > the sort of incremental improvements to HTML proposed by us at the 90 | > workshop. 91 | 92 | ## 2004-07 to 2004-12 93 | 94 | - [HTML `canvas` element created by the Safari team at Apple](http://ln.hixie.ch/?start=1089635050&count=1) 95 | and 96 | [first specified as part of Web Applications 1.0](http://web.archive.org/web/20041009144718/http://whatwg.org/specs/web-apps/current-work/). 97 | 98 | - [The possibility of an "HTML 5.0 specification" is mentioned](http://lists.w3.org/Archives/Public/public-whatwg-archive/2004Aug/0345.html) 99 | in a message from Anne van Kesteren on the WHATWG mailing list; and in a 100 | [later reply on the same list](http://lists.w3.org/Archives/Public/public-whatwg-archive/2004Nov/0030.html), 101 | Ian Hickson says that "at this point Web Apps [Web Applications 1.0] is 102 | basically HTML5"; subsequently, the term *HTML5* begins to be used in 103 | WHATWG discussions as a shorthand name for the Web Applications 1.0 spec. 104 | 105 | - [Ruby on Rails first released](http://en.wikipedia.org/wiki/Ruby_on_Rails#History) 106 | by David Heinemeier Hansson. Among other things, it becomes notable as 107 | one of the first server-side Web-application development frameworks that 108 | provide specific support for XHR-driven Web applications (what will in 109 | 2005 start to be referred to as "Ajax" applications). 110 | 111 | - [Opera begins to ship pre-installed on some mobile devices](http://www.kddi.com/english/corporate/news_release/2004/1006/), 112 | becoming -- three years before the release of iPhone and mobile Safari -- 113 | the first "full" mobile browser (non-WAP, JavaScript-enabled, using the 114 | same browser engine as desktop Opera) to generate any significant mobile 115 | browsing traffic to normal (non-WAP) websites (though the usage largely 116 | comes just from mobile phones in Japan, which at that time are still 117 | significantly more advanced than mobile devices elsewhere in the world). 118 | 119 | - [Web 2.0 Conference](http://web.archive.org/web/20041001091530/www.web2con.com/pub/w/32/program.html) 120 | takes place in San Francisco, eventually causing the term *Web 2.0* to be 121 | brought into general use. 122 | 123 | ## 2005-02 124 | 125 | - [Google Maps launched](http://en.wikipedia.org/wiki/Google_maps#History) 126 | in beta with support across all major browsers (Internet Explorer, Mozilla, 127 | Opera, and Safari), following just after the launch, two months earlier, of 128 | [Google Suggest](http://googleblog.blogspot.com/2004/12/ive-got-suggestion.html) 129 | as a Google "Labs" project. 130 | 131 | - [Ajax: A New Approach to Web Applications](http://www.adaptivepath.com/ideas/essays/archives/000385.php) 132 | by Jesse James Garrett; coining the term *Ajax* to describe XHR-driven 133 | modern Web applications, Garrett specifically mentions JSON as a "means 134 | of structuring data for interchange" in such applications, and cites 135 | Gmail, Google Suggest, Google Maps, and Flickr as examples. 136 | 137 | - [Prototype JavaScript Framework created](http://en.wikipedia.org/wiki/Prototype_JavaScript_Framework) 138 | by Sam Stephenson; included with Ruby on Rails, it's one of the first 139 | JavaScript libraries to include specific mechanisms for building 140 | XHR-driven applications. 141 | 142 | ## 2005-03 to 2005-06 143 | 144 | - [Cross-document messaging (`postMessage`)](http://web.archive.org/web/20050301091946/http://whatwg.org/specs/web-apps/current-work/) 145 | first specified, as part of Web Applications 1.0. 146 | 147 | - [CouchDB created](http://en.wikipedia.org/wiki/CouchDB#History) 148 | by Damien Katz; it's notable in being intended as a "database that 149 | completely embraces the web" -- using JSON, JavaScript, and HTTP, and 150 | fundamentally designed for serving Web applications. (More specifically, 151 | it's schema-less and non-relational, storing data as JSON-formatted 152 | semi-structured documents, built on a non-SQL, JavaScript-based query 153 | mechanism -- with a MapReduce-driven view model -- and with a RESTful 154 | HTTP API for consuming and exposing data in JSON (PUT/POST data as JSON 155 | objects, and GET results as JSON objects). 156 | 157 | - [Acid2](http://en.wikipedia.org/wiki/Acid2) published by Ian Hickson as a 158 | means to test the level of standards conformance in Web browsers. 159 | 160 | - [Opera 8](http://en.wikipedia.org/wiki/History_of_the_Opera_web_browser#Version_8) 161 | released; notable in that it's the first release version of Opera with 162 | (limited) XHR support, which finally makes XHR available across all major 163 | browser engines. 164 | 165 | - [The Web Platform - Browsers and Applications](http://www.w3.org/2005/Talks/0513-webplatform/) 166 | talk presented by Dean Jackson in the W3C track at WWW2005, with the 167 | goals of the "Web Platform" outlined as: 168 | 169 | * To (better) enable the Web as an application platform (on all devices) 170 | * To help users by requiring support for standards in the browser. 171 | * To give Web developers a better programming environment (with new 172 | interfaces). 173 | 174 | Going forward, the term "the Web Platform" will come into increasing use 175 | specifically for describing the standard set of client-side technologies 176 | made available in browsers, for building modern Web applications. 177 | 178 | - [script.aculo.us created](http://en.wikipedia.org/wiki/Script.aculo.us) 179 | by Thomas Fuchs; built on top of the Prototype JavaScript Framework and 180 | included in Ruby on Rails, it's one of the first "Ajax" script libraries 181 | to come into wide use. 182 | 183 | ## 2005-07 to 2005-11 184 | 185 | - [`` (HTML5 doctype) first introduced](http://web.archive.org/web/20050701075402/http://www.whatwg.org/specs/web-apps/current-work/). 186 | 187 | - [Client-side local storage](http://www.whatwg.org/specs/web-apps/2005-09-01/) 188 | first specified, as part of Web Applications 1.0. 189 | 190 | - [del.icio.us begins providing a RESTful HTTP API that makes data available in JSON](http://inkdroid.org/journal/2005/09/21/delicious-json/); 191 | within the next three years, Flickr, Yahoo, Google, and most other major 192 | providers of Web-based services begin to provide similar HTTP APIs that 193 | expose data formatted in JSON. 194 | 195 | - [What Is Web 2.0](http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html) 196 | article by Tim O'Reilly. Subsequent discussions of the term *Web 2.0* 197 | often cite this article; excerpt: 198 | 199 | > It's clear that standards and solutions [...] will enable the next 200 | > generation of applications. [...] AJAX is also a key component of Web 201 | > 2.0 applications such as Flickr[...] We're entering an unprecedented 202 | > period of user interface innovation, as web developers are finally able 203 | > to build web applications as rich as local PC-based applications. 204 | 205 | - [Web API](http://www.w3.org/2006/webapi/) and 206 | [Web Application Formats](http://www.w3.org/2006/appformats/) 207 | Working Groups chartered at the launch of the W3C 208 | [Rich Web Client Activity](http://www.w3.org/News/2005#x200501115c). 209 | 210 | The Web API Working Group mission is described as being to "enable 211 | improved client-side application development on the Web" and its a scope 212 | includes, among other things, documenting the Window and XMLHttpRequest 213 | (XHR) interfaces and the `setTimeout` method, as well as specifying 214 | "network communication methods" and a means for "persistent storage on 215 | the client" to facilitate "more advanced Web applications, enabling them 216 | to store user preferences and possibly work in an offline environment, 217 | such as a laptop or mobile phone with intermittent connectivity". 218 | 219 | ## 2006-01 to 2006-02 220 | 221 | - [Firebug](https://addons.mozilla.org/en-US/firefox/addon/firebug/versions/?page=5#version-0.2) 222 | first version released by Joe Hewitt. 223 | 224 | - [Opera Mini](http://en.wikipedia.org/wiki/Opera_Mini) 225 | released; it will play a role in expanding Web access to more parts of 226 | the world, and will end up consistently accounting for a significant 227 | percentage of worldwide mobile Web-browsing traffic. 228 | 229 | - [JSON Internet Draft published](http://ietfreport.isoc.org/all-ids/draft-crockford-jsonorg-json-00.txt) 230 | by Doug Crockford; however, it 231 | [had already been documented by Crockford elsewhere](https://web.archive.org/web/20030417010540/http://www.crockford.com/JSON/) 232 | going back to at least late 2002, and a number of major Web-based 233 | services had already started to provide APIs that exposed data formatted 234 | in JSON. 235 | 236 | - [HTML parsing algorithm](http://web.archive.org/web/20060202011253/http://whatwg.org/specs/web-apps/current-work/) 237 | first specified, as part of Web Applications 1.0. 238 | 239 | ## 2006-07 to 2006-11 240 | 241 | - [Twitter first launched](http://techcrunch.com/2006/07/15/is-twttr-interesting/) 242 | and 243 | [Facebook first opened widely](http://en.wikipedia.org/wiki/Timeline_of_Facebook#2006) 244 | for all users to join. 245 | 246 | - [jQuery 1.0](http://blog.jquery.com/2006/08/26/jquery-10/) released. 247 | 248 | - [Internet Explorer version 7](http://en.wikipedia.org/wiki/Internet_Explorer#Version_7) 249 | released with CSS and DOM improvements -- five years after the release of IE6. 250 | 251 | - [Reinventing HTML](http://dig.csail.mit.edu/breadcrumbs/node/166) 252 | posting by Tim Berners-Lee: 253 | 254 | > Some things are clearer with hindsight of several years. It is 255 | > necessary to evolve HTML incrementally. The attempt to get the world to 256 | > switch to XML, including quotes around attribute values and slashes in 257 | > empty tags and namespaces all at once didn't work[...] The plan is to 258 | > charter a completely new HTML group. Unlike the previous one, this one 259 | > will be chartered to do incremental improvements to HTML, as also in 260 | > parallel xHTML. 261 | 262 | - [Proposed charter](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0045.html) 263 | for HTML Working group posted by Ian Hickson (following 264 | [the earlier posting of shorter proposed charter](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0000.html), 265 | [specific feedback](http://lists.w3.org/Archives/Public/www-archive/2006Nov/0000.html) 266 | and some 267 | [public discussion about charter review](http://lists.w3.org/Archives/Public/www-archive/2006Nov/thread.html#msg53)). 268 | 269 | ## 2007-03 to 2007-05 270 | 271 | - [Fifth W3C HTML Working Group](http://www.w3.org/2007/03/HTML-WG-charter.html) 272 | chartered (though only the second W3C HTML working group to focus on the core 273 | HTML language), with a mission *to continue the evolution of HTML (including 274 | classic HTML and XML syntaxes)* and with a statement that *this group 275 | will maintain and produce incremental revisions to the HTML specification [to 276 | produce] a language evolved from HTML4 for describing the semantics of 277 | documents and applications on the World Wide Web.* 278 | 279 | - [`video` and `audio` elements added to the HTML spec](http://html5.org/r/394-699). 280 | 281 | - [Google Gears](http://gearsblog.blogspot.com/2007/05/posted-by-aaron-boodman-and-erik.html) 282 | released; some of its key features, such as its "workerpool" mechanism, 283 | eventually become standard parts of the Web platform, and by the end of 284 | 2009 its development will end up being permanently halted. 285 | 286 | ## 2007-06 to 2007-12 287 | 288 | - [iPhone](http://en.wikipedia.org/wiki/History_of_the_iPhone#World_timeline) 289 | first released; notable among other things in that it doesn't include 290 | support for Adobe Flash, it will end up consistently accounting for 291 | significantly more mobile Web-browsing traffic than any other mobile 292 | device. 293 | 294 | - [HTML "offline Web applications" feature introduced](http://html5.org/tools/web-apps-tracker?from=848&to=1115) 295 | (`applicationCache` interface, _aka_ appCache) 296 | 297 | - [CSS Transforms](https://www.webkit.org/blog/130/css-transforms/) 298 | and 299 | [CSS Transitions](https://www.webkit.org/blog/138/css-animation/) 300 | (`transform-*` and `transition-*` properties) created by the Safari team at Apple. 301 | 302 | - [Downloadable-fonts support added to WebKit](https://www.webkit.org/blog/124/downloadable-fonts/); 303 | (`@font-face` rule). Eventually, by mid-2009, downloadable fonts will be 304 | supported in all major browsers. (Note that Internet Explorer was the 305 | first to have downloadable-fonts support, starting with the release of 306 | IE4 in 1997 -- and the feature had actually been part of the CSS2.0 307 | Recommendation published in 1998.) 308 | 309 | - [Futhark JavaScript engine released in beta](http://my.opera.com/desktopteam/blog/2007/10/25/opera-9-5-beta-released) 310 | as part of Opera 9.5; for a time it will be the fastest JavaScript engine 311 | on the market, and help to initiate a JavaScript-engine performance race 312 | among browser projects, starting in mid-2008. 313 | 314 | - [Android mobile-device platform announced](http://www.openhandsetalliance.com/press_110507.html); 315 | it is notable for including a mobile browser that uses WebKit as its 316 | browser engine; however, it will be nearly a year before any Android 317 | devices actually begin to ship. 318 | 319 | - [SunSpider JavaScript benchmark introduced](https://www.webkit.org/blog/152/announcing-sunspider-09/) 320 | by the Safari team at Apple; during the latter half of 2008 and after, it 321 | will become widely used by other major browser projects in documenting 322 | the relative performance improvements in their JavaScript engines. 323 | 324 | ## 2008-01 to 2008-06 325 | 326 | - [First W3C Working Draft of HTML5 published](http://www.w3.org/News/2008.html#entry-6935). 327 | 328 | - [Acid3](http://en.wikipedia.org/wiki/Acid3) 329 | published by Ian Hickson as a means to test the level of standards 330 | conformance in Web browsers. 331 | 332 | - [GitHub launched](https://github.com/blog/40-we-launched). 333 | 334 | - [SquirrelFish JavaScript engine announced](https://www.webkit.org/blog/189/announcing-squirrelfish/) 335 | by the Safari team at Apple; it's an incremental rewrite of Safari's 336 | "JavaScriptCore" engine to turn it into a bytecode interpreter, resulting 337 | in large performance improvements. 338 | 339 | During the following months, other browser projects begin to rewrite 340 | their JavaScript engines in a race that over the following next few years 341 | eventually results in vastly improved overall speed of JavaScript 342 | execution across all major browsers. 343 | 344 | - [W3C Web Applications Working Group launched](http://www.w3.org/blog/news/archives/286); 345 | the group merges the existing Web APIs Working Group and Web Application 346 | Formats Working Group into a single group, with a mission to *provide 347 | specifications that enable improved client-side application development 348 | on the Web* 349 | 350 | - [Geolocation API first Editor's Draft written and announced](http://lists.w3.org/Archives/Public/public-geolocation/2008Jun/0000.html) 351 | by Andrei Popescu. 352 | 353 | ## 2008-07 to 2008-10 354 | 355 | - [Web Sockets and Web Workers first specified](http://html5.org/tools/web-apps-tracker?from=1835&to=1968). 356 | 357 | - [Geolocation API ships in Google Gears 0.4](http://gearsblog.blogspot.jp/2008/08/gears-04-is-here.html), 358 | the first implementation of the Geolocation API to be made available. 359 | 360 | - [Firefox developer builds begin shipping with TraceMonkey](http://news.cnet.com/8301-1001_3-10023723-92.html), 361 | a JIT-based JavaScript engine (compiling JavaScript to native machine 362 | code) that provides greatly improved JavaScript performance. 363 | 364 | - [Google Chrome first released](http://googleblog.blogspot.jp/2008/09/google-chrome-now-live.html), 365 | with WebKit as its browser engine, and notable for being the first 366 | release version of a browser to ship with a JIT-based JavaScript engine, 367 | V8, which provides greatly improved JavaScript performance on par with 368 | Mozilla's TraceMonkey (which had been released to developers less that a 369 | month earlier). 370 | 371 | - [WebKit announces SquirrelFish Extreme](https://www.webkit.org/blog/214/introducing-squirrelfish-extreme/), 372 | a new JIT-based JavaScript engine with performance on par with V8 and 373 | TraceMonkey. 374 | 375 | Over the coming months, the browser projects will all race with each 376 | other further to incrementally improve the performance of their 377 | JavaScript engines, with the result over the long term being a vast 378 | improvement in the overall speed of JavaScript execution across all major 379 | browsers -- which among other things ends up enabling browsers to behave 380 | performantly with JavaScript-heavy Web application even on mobile devices 381 | with relatively limited RAM and CPU resources. 382 | 383 | - [First Android device ships](http://en.wikipedia.org/wiki/HTC_Dream#History): 384 | the HTC dream, running Android 1.6; notable in that it's the first 385 | non-iPhone smartphone to ship with a WebKit-based browser. Other 386 | Android-based mobile devices will begin to ship in 2009, resulting in 387 | Android devices accounting for a significant percentage of 388 | mobile-browsing traffic by the end of 2010, when Android becomes the 389 | most widely used smartphone platform worldwide. 390 | 391 | - [Geolocation API ships in Firefox 3.1 beta](http://arstechnica.com/information-technology/2008/10/first-look-firefox-3-1-beta-1-officially-released/). 392 | 393 | ## 2009-02 to 2009-06 394 | 395 | - [CSS Animations created by the Safari team at Apple](https://www.webkit.org/blog/324/css-animation-2/) 396 | (`@keyframes` rule and `animation-*` properties). 397 | 398 | - [Internet Explorer version 8](http://en.wikipedia.org/wiki/Internet_Explorer#Windows_Internet_Explorer_8) 399 | released; it is the first version of IE to pass [Acid2](http://en.wikipedia.org/wiki/Acid2). 400 | 401 | - [Node.js first released](https://github.com/joyent/node/commit/80eed19612db0fe54191683e8a9f0bc5c1ca4ff6) 402 | by Ryan Dahl; it's a software platform notable for being built around the 403 | V8 JavaScript engine -- providing a way for developers to do server-side 404 | development in JavaScript using a non-threaded, non-blocking "evented 405 | I/O"-based, asynchronous callback-driven programming model similar to the 406 | client-side event-loop-based programming model provided by Web browsers. 407 | 408 | - [Geolocation API support ships in iOS 3.0](http://radar.oreilly.com/2009/06/geolocating-your-iphone-users.html), 409 | making the iPhone the first mobile device with native support for the 410 | Geolocation API in its browser. (Support for Android devices will ship a 411 | few months later, in Android 2.0). 412 | 413 | ## 2009-09 414 | 415 | - [WebGL support lands in Firefox Nightly](https://hacks.mozilla.org/2009/09/webgl-for-firefox/) 416 | and, shortly after, also 417 | [lands in WebKit nightlies](https://www.webkit.org/blog/603/webgl-now-available-in-webkit-nightlies/) 418 | and [Chrome developer builds](https://groups.google.com/d/msg/chromium-dev/DusnVs_TGGA/Z9p_p3joTy4J) 419 | -- thought the WebGL specification 420 | [isn't actually published until December 2009](http://www.khronos.org/webgl/public-mailing-list/archives/0912/msg00000.html). 421 | 422 | ## 2010-02 423 | 424 | - [Google Gears development officially stopped](http://gearsblog.blogspot.com/2010/02/hello-html5.html) 425 | by the Gears team at Google, following a gradual shift "towards bringing 426 | all of the Gears capabilities into web standards like HTML5". 427 | 428 | ## 2010-04 429 | 430 | - [Steve Jobs "Thoughts on Flash"](http://www.apple.com/hotnews/thoughts-on-flash/); 431 | excerpt: 432 | 433 | > [...] the mobile era is about low power devices, touch interfaces and 434 | > open web standards – all areas where Flash falls short[‥.] Rather than 435 | > use Flash, Apple has adopted HTML5, CSS and JavaScript – all open 436 | > standards[...] Perhaps Adobe should focus more on creating great HTML5 437 | > tools for the future, and less on criticizing Apple for leaving the 438 | > past behind. 439 | 440 | ## 2011-03 441 | 442 | - [Internet Explorer version 9](http://en.wikipedia.org/wiki/Internet_Explorer_9) 443 | released, with major improvements in standards support (including support 444 | for the Geolocation API, SVG and the HTML `canvas` and `video` elements). 445 | 446 | - [Video conferencing and peer-to-peer communication](http://html5.org/tools/web-apps-tracker?from=5944&to=5945) 447 | section added to the WHATWG HTML spec by Ian Hickson. 448 | 449 | [Announced on the WHATWG mailing list](http://lists.w3.org/Archives/Public/public-whatwg-archive/2011Mar/0238.html), 450 | this new section of the HTML spec introduces the `getUserMedia` method, 451 | `PeerConnection` interface, and `MediaStream` interface (initially just 452 | named `Stream`). The content of the section will eventually be forked 453 | by the W3C WebRTC Working Group to create the 454 | [WebRTC spec](http://dev.w3.org/2011/webrtc/editor/webrtc.html), but even 455 | at this point in 2011 when it is first introduced, it already provides 456 | for all of the following: 457 | 458 | > Getting a multimedia stream (video, audio, or both) from local devices 459 | > (video cameras, microphones, Web cams) or from prerecorded files 460 | > provided by the user; Recording such streams locally; Connecting to 461 | > remote peers using NAT-traversal technologies such as ICE, STUN, and 462 | > TURN; Sending the locally-produced streams to remote peers and 463 | > receiving streams from remote peers; Displaying such streams (both the 464 | > locally-produced ones and the remotely-obtained ones) locally using the 465 | > video or audio elements; Sending arbitrary data to remote peers. 466 | 467 | ## 2011-11 468 | 469 | - [Flash Player for mobile devices end-of-lifed by Adobe](http://blogs.adobe.com/conversations/2011/11/flash-focus.html); 470 | the news is widely interpreted as a major shift by Adobe toward HTML5 and 471 | away from Flash; excerpt from the announcement: 472 | 473 | > HTML5 is now universally supported on major mobile devices, in some 474 | > cases exclusively. This makes HTML5 the best solution for creating and 475 | > deploying content in the browser across mobile platforms. 476 | 477 | ## 2012-02 478 | 479 | - [Adobe reduces Flash roadmap to just two areas: gaming and premium video](http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html); 480 | the news is widely interpreted as a further focusing by Adobe away from 481 | Flash and toward HTML5 and other "modern web technologies": 482 | 483 | > With the growth of competition in the browser market, browser vendors 484 | > are increasingly innovating and providing functionality that makes it 485 | > possible to deploy rich motion graphics directly via browser 486 | > technologies, a role once served primarily by Flash Player. 487 | > Increasingly, rich motion graphics are being deployed directly via the 488 | > browser using HTML5, CSS3, JavaScript and other modern web 489 | > technologies. Adobe expects that this trend will continue and 490 | > accelerate, and Adobe will continue to play an active role in this 491 | > space. 492 | --------------------------------------------------------------------------------