�ݺ�ߣ

1. The Future of the Web

2. TAG TC39

3. Legrand Star story

7. maincontent component

12. "It sucks!" Adding features to the web this way is really annoying. You have to hack in deep and multiple libraries that do this usually don't play nicely together.

13. We prefer a decentralized design

14. We like pictureﬁll

15. We like jQuery

16. Why?

17. Iterate Without Risk "Don't break the web" is the mantra of standards and browser vendors. Experimentation via libraries doesn't have this problem!

18. Domain-Specific Solutions Synthesizing all use-cases into a single "standard" is very hard. Allowing domain-specific solutions relieves the pressure and helps flesh out the use-cases.

19. Simpler Standardization If everything goes well and it makes sense to standardize, it's a lot easier to do that when the developer ecosystem has been iterating on solutions for a while.

20. There's No Rush The standards process often jumps on some problem, like oﬄine or local storage, because it's perceived as urgent. Library solutions reduce the urgency and the mistakes that come from rushing.

21. Feedback Loop

22. "It sucks"

23. App Cache

26. Centrally Planned New Capabilities

28. www.yehudakatz.com

33. Gastropub wolf street art Austin actually. Blue bottle cliche Marfa, scenester roof party before they sold out Godard. www.yehudakatz.com

35. Gastropub wolf street art Austin actually. Blue bottle cliche Marfa, scenester roof party before they sold out Godard. www.yehudakatz.com <img src=/slideshow/future-of-the-web-22738028/22738028/"face.png">

40. Black Box You can add oﬄine caching, but it's a black box that's totally controlled by the relatively slow-moving standards process.

42. Reported: 2011-11-05

43. Reported: 2011-11-05 2012-06-14 Ian 'Hixie' Hickson I've added the idea in comment 27 to the WHATWG spec

44. Reported: 2011-11-05 2012-06-14 Ian 'Hixie' Hickson I've added the idea in comment 27 to the WHATWG spec 2013-06-05: implemented?

46. slightlyoﬀ / NavigationController

50. www.yehudakatz.com controller.js

56. Gastropub wolf street art Austin actually. Blue bottle cliche Marfa, scenester roof party before they sold out Godard. www.yehudakatz.com controller.js

59. Gastropub wolf street art Austin actually. Blue bottle cliche Marfa, scenester roof party before they sold out Godard. www.yehudakatz.com <img src=/slideshow/future-of-the-web-22738028/22738028/"face.png"> controller.js

75. App Cache as a Library You can now implement app cache as a library, and if the initial implementation is insuﬃcient, a much wider community can iterate on it. Domain-speciﬁc solutions can also emerge.

76. Custom Elements

77. import { imageBitmapStream, HTMLCanvasElement } from "web/html/canvas"; import fetch from "web/network/fetch"; class CustomImage extends HTMLCanvasElement { readyCallback() { fetch(this.src).pipe(imageBitmapStream).pipe(this); } } document.register('custom-image', CustomImage); <html> <custom-image src=/slideshow/future-of-the-web-22738028/22738028/"logo.png"></custom-image> </html>

78. Standards Focus on Capabilities Standards bodies are needed to expose new capabilities in a cross-browser way. Browser vendors working through the standards process ensure that these capabilities are secure and eﬃcient. In the short term, this also means exposing hooks into HTML and CSS, so that library authors can add new high-level features without rewriting the entire stack.

79. Developers Iterate on Higher Level APIs More capabilities and hooks into the high level APIs of the platform mean that library authors can iterate on features that would previously have required native implementations.

80. Browser Vendors seed the discussion Increasingly, browser vendors are seeding the discussion by providing libraries like X-Tags, Polymer, MDV, Persona, etc. This gives developers a place to start and lets them use "experimental" features right away without fear of breaking the web.

81. Let a Thousand MathMLs Bloom! Finally, by making it possible for libraries to build high- level features that compose well and feel native, we enable niche communities to build up their own declarative vocabularies. Communities with special caching needs can make their own app cache.

82. The future of the web is decentralized innovation The web got started with the radical idea that document authors shouldn't need permission from a central authority to publish. Why not apply the same ideas to the standards process itself?

�ݺ�ߣ

Future of the Web - Yehuda Katz

More Related Content

Future of the Web - Yehuda Katz