-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
755 lines (643 loc) · 28.3 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>WebAssembly</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!-- style inline <code> -->
<style>
.reveal :not(pre) > code {
color: #e3ceab;
font-size: 75%;
}
.reveal .yay {
color: #1b91ff;
font-size: 125%;
}
.reveal .blue {
color: #1b91ff;
}
.reveal .snowmen-list {
list-style: none;
margin-left: 0;
padding-left: 1em;
text-indent: -1em;
}
.reveal .snowmen-list li:before {
content: "☃";
padding-right: .5em;
}
.reveal .squishedtable td {
padding: 2px;
}
</style>
</head>
<body>
<div class="reveal"><div class="slides">
<section>
<h1>WebAssembly</h1>
<p><small>
lukewagner.github.io/wasm-talk-2017<br><br>
Luke Wagner / @luke_wagner
</small></p>
</section>
<section>
<p>Questions welcome!</p>
<p class="fragment">This is pretty low-level stuff; if you have a question, chances are everyone else does too!</p>
</section>
<section>
<h2>About me</h2>
<p>Mozilla Firefox/SpiderMonkey hacker for 8 years<p>
<table class="squishedtable">
<tr>
<td><img src="trace.jpg" /><br><center><small>2008 - 2011</small></center></td>
<td><img src="jaeger.jpg" /><br><center><small>2010 - 2013</small></center></td>
<td><img src="ion.jpg" /><br><center><small>2012 -</small></center></td>
<td><img src="odin.jpg" /><br><center><small>2013 - </small></center></td>
<td><img src="baldr.jpg" /><br><center><small>2016 - </small></center></td>
</tr>
</table>
<p>Member of WebAssembly W3C Community Group</p>
</section>
<section>
<h2>caniuse?</h2>
<img src="caniuse.png" />
</section>
<section>
<h2>caniuse?</h2>
<img src="caniuse2.png" />
</section>
<section>
<h2>Outline</h2>
<ul>
<li>What is WebAssembly?</li>
<li>Short Tour of WebAssembly</li>
<li>Accessing Web APIs from WebAssembly</li>
<li>Beyond compiling C/C++</li>
<li>Frequently Asked Questions</li>
</ul>
</section>
<section>
<h2>What is WebAssembly?</h2>
<p>
An <span class="fragment highlight-current-blue"><em>emerging standard</em></span>
which defines:
</p>
<ol>
<li>
a <span class="fragment highlight-current-blue">compact</span>,
<span class="fragment highlight-current-blue">portable</span>
<span class="fragment highlight-current-blue"><em>binary format</em></span> which is
<span class="fragment highlight-current-blue">fast to load</span> and runs
<span class="fragment highlight-current-blue">safely</span> at
<span class="fragment highlight-current-blue">predictably near-native speed</span>
</li>
<li>
a <span class="fragment highlight-current-blue">1:1 <em>text format</em></span>
<span class="fragment highlight-current-blue">rendered by tools</span> when
<span class="fragment highlight-current-blue">viewing source</span>
</li>
</ol>
</section>
<section>
<p>Multiple valid ways to look at WebAssembly:</p>
<ol>
<li>virtual CPU</li>
<li>evolution of asm.js</li>
<li>new JavaScript power</li>
</ol>
<p>Depends on where you are coming from</p>
</section>
<section>
<h2>1. Virtual CPU</h2>
<p>Not a programming language</p>
<p class="fragment">Compile <em>from</em> programming languages</p>
<p class="fragment">As close to real CPUs as <em>safety</em>/<em>portability</em> allow</p>
</section>
<section>
<h3>Safety matters!</h3>
<p class="fragment">WebAssembly doesn't change the security model of the Web</p>
<p class="fragment">Pointers are <em>checked indices</em>, not raw addresses</p>
<p class="fragment">Memory access is like JS array access: out-of-bounds throws</p>
</section>
<section>
<h3>Portability matters!</h3>
<p class="fragment">Changing browser/version/device shouldn't break things</p>
<p class="fragment">Just like upgrading your x86 CPU shouldn't break things</p>
<p class="fragment">So WebAssembly specifies <em>everything</em>*</p>
</section>
<section>
<table>
<tr>
<th>WebAssembly</th>
<th></th>
<th>x86/x64</th>
<th>ARM/ARM64</th>
</tr>
<tr>
<td><code>i32.add</code></td>
<td>↦</td>
<td><code>addl</code></td>
<td><code>ADD</code></td>
</tr>
<tr>
<td><code>call</code></td>
<td>↦</td>
<td><code>call</code></td>
<td><code>BL</code></td>
</tr>
<tr>
<td><code>i32.load</code></td>
<td>↦</td>
<td>check + <code>mov</code></td>
<td>check + <code>LDR</code></td>
</tr>
<tr>
<td>infinite stack/locals</td>
<td>↦</td>
<td>8/16 registers</td>
<td>16/32 registers</td>
</tr>
</table>
</section>
<section>
<h2>2. Evolution of asm.js</h2>
<p class="fragment">
<em>asm.js</em> is an extraordinarily optimizable, low-level
<em>subset of JavaScript</em> that can be compiled from
languages like C/C++.
</p>
<p class="fragment">
Because it's <em>just JavaScript</em>, runs well on all
browsers <em>today</em>.
</p>
<p class="fragment">
Special optimizations added to Firefox, Edge and Chrome.
</p>
<p class="fragment">
Safari includes asm.js in their JetStream benchmark.
</p>
</section>
<section>
<p>How do you get asm.js?</p>
<img src="emscripten.png" />
<p>C/C++ ⇒ clang/LLVM ⇒ Emscripten ⇒ asm.js</p>
</section>
<section>
<h3>asm.js timeline</h3>
<table>
<tr>
<td>2009 - 2012</td>
<td>
Mozilla Research experiments:<br>
<em>Emscripten</em>: C/C++ to JS compiler/toolchain<br>
<em>asm.js</em>: optimize Emscripten-style output
</td>
</tr>
<tr>
<td>2013 - 2014</td>
<td>
Published <em>asm.js</em> subset, shipped optimizations
in Firefox, demonstrated on large game engines
</td>
</tr>
<tr>
<td>2015 - 2016</td>
<td>
<p>Other browsers add optimizations</p>
<p>Adobe, AutoDesk, Epic, Facebook, Mega, Unity, and more shipping with Emscripten/asm.js</p>
<p>Cross-browser work begins on WebAssembly</p>
</td>
</td>
</table>
</section>
<section>
<p>Why are developers using asm.js?</p>
<ul>
<li class="fragment">avoid plugins (deprecation, friction, security)</li>
<li class="fragment">bring existing applications to the Web (too big to rewrite)</li>
<li class="fragment">port high-performance C/C++ libraries for use by JS</li>
<li class="fragment">predictable near-native performance (compared to JS)</li>
</ul>
</section>
<section>
<p>Why wasn't asm.js enough?</p>
<ol>
<li class="fragment">parse time (especially on mobile)</li>
<li class="fragment">over-the-wire size (with and without compression)</li>
<li class="fragment">new features hard in JS: threads, dynamic linking, ...</li>
<li class="fragment">reduce browser variance</li>
</ol>
</section>
<section>
<p>WebAssembly as binary encoding of asm.js (with tweaks)</p>
<table>
<tr>
<th>asm.js</th>
<th></th>
<th>WebAssembly</th>
</tr>
<tr>
<td><code>(x+y)|0</code></td>
<td>↦</td>
<td><code>i32.add</code></td>
</tr>
<tr>
<td>☹</td>
<td>↦</td>
<td><code>i64.add</code></td>
</tr>
<tr>
<td><code>f()|0</code></td>
<td>↦</td>
<td><code>call</code></td>
</tr>
<tr>
<td><code>HEAP32[i>>2]|0</code></td>
<td>↝</td>
<td><code>i32.load</code></td>
</tr>
</table>
<p class="fragment">raw: WebAssembly is ~42% smaller</p>
<p class="fragment">gzipped: WebAssembly is ~23% smaller</p>
<p class="fragment">Decoding WebAssembly ~10x faster than parsing JS</p>
</section>
<section>
<h2>3. New JavaScript power</h2>
<p>Ability to efficiently load large code +</p>
<p>predictable near-native performance =</p>
<p>Powerful JavaScript library-building tool</p>
</section>
<section>
<p>What sort of libraries? Today, using asm.js:</p>
<ul>
<li>compress before upload (Facebook)</li>
<li>video (de)muxing (Twitch)</li>
<li>image filters (Adobe Lightroom)</li>
<li>codec polyfill (Wikipedia)</li>
<li>3D mapping (BA3)</li>
<li>custom audio mixing (Faust)</li>
<li>crypto (Mega)</li>
<li>physics engine (PlayCanvas)</li>
<li>language detection (FFOS)</li>
<li>face detection (various)</li>
<li>...</li>
</ul>
</section>
<section>
<p>Tomorrow: Web Frameworks!</p>
<p class="fragment">What?!! But it's all DOM and strings and stuff!</p>
<p class="fragment">Not anymore: virtual DOM, reconciliation, bytecode VMs, ...</p>
</section>
<section>
<p><a href="https://www.youtube.com/watch?v=PU94cgLuw9I">From Tom Dale's 2017 JSConf.eu talk</a></p>
<img src="frameworks-are-compilers.png" />
</section>
<section>
<p><a href="https://www.youtube.com/watch?v=3GHJ4cbxsVQ">From Lin Clark's 2017 ReactEurope talk</a></p>
<img src="wasm-react-talk.png" />
</section>
<!---------------------------------------------------------------------------------- -->
<section>
<h2>Outline</h2>
<ul>
<li>What is WebAssembly? ✔</li>
<li>Short Tour of WebAssembly</li>
<li>Accessing Web APIs from WebAssembly</li>
<li>Beyond compiling C/C++</li>
<li>Frequently Asked Questions</li>
</ul>
</section>
<section>
<p><img src="construction.gif" /></p>
<p>WebAssembly is being specified and shipped <em>iteratively</em></p>
<p>What's released today is the Minimum Viable Product (MVP)</p>
<p>There is a <em>lot</em> more to do: standard <em>and</em> toolchain</p>
<p>Speculative features are marked with ☃</p>
</section>
<section>
<p>Today, WebAssembly primarily compiled from C/C++:</p>
<p>C/C++ ⇒ clang/LLVM ⇒ Emscripten ⇒ WebAssembly</p>
<div class="fragment">
<p>Ongoing work on:</p>
<ul class="snowmen-list">
<li>Upstream LLVM backend</li>
<li>Rust-to-WebAssembly</li>
</ul>
</div>
</section>
<section>
<p>Start with some C code:</p>
<pre><code class="c" data-trim>
// demo.c
MODULE_EXPORT
int add(int lhs, int rhs) {
return lhs + rhs;
}
</code></pre>
<p>then compile to <code>wasm</code>:</p>
<pre><code class="bash" data-trim>
☃ clang-wasm demo.c -o demo.wasm
</code></pre>
</section>
<section>
<p>Render the binary as text:</p>
<pre><code class="bash" data-trim>
$ wasm2wat demo.wasm | less
</code></pre>
<pre><code class="lisp" data-trim>
(module
(func (export "add") (param i32 i32) (result i32)
get_local 0
get_local 1
i32.add
)
)
</code></pre>
<p class="fragment">Tour of opcodes out of scope, see <a href="https://webassembly.github.io/spec/syntax/instrindex.html">draft spec</a></p>
</section>
<section>
<p>Compile the <code>.wasm</code> using JS <code>WebAssembly</code> API</p>
<pre><code class="javascript" data-trim data-noescape>
fetch('demo.wasm').then(response =>
<span class="fragment highlight-current-blue">response.arrayBuffer()</span>
).then(bytecode =>
<span class="fragment highlight-current-blue">WebAssembly.instantiate(bytecode)</span>
).then(({instance}) =>
alert("1 + 2 = " + <span class="fragment highlight-current-blue">instance.exports.add(1, 2)</span>);
);
</code></pre>
</section>
<section>
<h2>Debug Demo</h2>
<script>
function demoClick() {
fetch('demo.wasm').then(response =>
response.arrayBuffer()
).then(buffer =>
WebAssembly.instantiate(buffer)
).then(({instance}) =>
alert("1 + 2 = " + instance.exports.add(1, 2))
);
}
</script>
<ol>
<li>Currently, works best in Firefox Nightly</li>
<li>Open the Debugger</li>
<li><button onclick='demoClick()'>Click this Button</button></li>
<li>See <code>wasm://</code> URL appear</li>
<li>Place breakpoint in wasm and re-click</li>
</ol>
</section>
<section>
<p>Standardized and coming soon:</p>
<pre><code class="js" data-trim>
WebAssembly.instantiate(fetch('demo.wasm')).then(({instance}) =>
alert("1 + 2 = " + instance.exports.add(1, 2));
);
</code></pre>
<p>Allows browser to do streaming and caching</p>
</section>
<section>
<p>☃ ES Module integration:</p>
<pre><code class="javascript" data-trim>
<script type='module'>
import add from 'demo.wasm';
alert("1 + 2 = " + add(1, 2));
</script>
</code></pre>
<p class="fragment">WebPack integration <a href="https://github.com/webpack/webpack/labels/Web%20Assembly">starting</a></p>
<p class="fragment">Lot more work to do here to integrate with modular workflow!</p>
</section>
<section>
<p>WebAssembly can call JavaScript too!</p>
<pre><code class="c" data-trim>
// main.c
// Think: import {printInt} from 'logger';
extern MODULE_IMPORT("logger") void printInt(int);
int main() {
printInt(42);
}
</code></pre>
<p>JS functions are <em>imported</em> (just as with an ES Module)</p>
</section>
<section>
<p>☃ With ES Module integration, we could write:</p>
<pre><code class="js" data-trim>
// logger.js
export var printInt = i => console.log(i);
</code></pre>
<pre><code class="html" data-trim>
<!-- index.html -->
<script type='module' src='main.wasm'></script>
</code></pre>
<br>
<div class="fragment">
<p>Today, pass in JS function using the <code>WebAssembly</code> API:</p>
<pre><code class="js" data-trim>
function printInt(i) { console.log(i) }
WebAssembly.instantiate(fetch('main.wasm'), {logger:{printInt}});
</code></pre>
</div>
</section>
<section>
<p>What we really want to see is the <em>source language</em></p>
<p class="fragment">Source Maps actually map naturally onto WebAssembly</p>
<p class="fragment">Still need to add mappings for <em>variable names</em></p>
<p class="fragment"><a href="source-maps-demo/pi.html">Demo</a></p>
<p class="fragment">More work to do here...</p>
</section>
<!---------------------------------------------------------------------------------- -->
<section>
<h2>Outline</h2>
<ul>
<li>What is WebAssembly? ✔</li>
<li>Short Tour of WebAssembly ✔</li>
<li>Accessing Web APIs from WebAssembly</li>
<li>Beyond compiling C/C++</li>
<li>Frequently Asked Questions</li>
</ul>
</section>
<section>
<p>What APIs look like on a traditional VM:</p>
<img src="traditional-vm-platform.png" />
<p> </p>
</section>
<section>
<p>The Web started out different:</p>
<img src="old-web-platform.png" />
</section>
<section>
<p>But the Web has changed a lot since then</p>
<img src="web-platform-1.png" />
<p>and is starting to resemble a traditional virtual platform</p>
</section>
<section>
<p>... with some special "Webby" properties like:<p>
<img src="web-platform-2.png" />
<p class="fragment">So where does WebAssembly fit in?</p>
</section>
<section>
<img src="web-platform-wasm.png" />
</section>
<section>
<p>Today, WebAssembly only gets to Web APIs by "thunking" through JavaScript</p>
<p>Emscripten maps common C/C++ interfaces to Web APIs:</p>
<pre><code class="c" data-trim>
#include <SDL/SDL.h>
#include <stdio.h>
int main(int argc, char **argv) {
SDL_Init(SDL_INIT_VIDEO);
SDL_Surface *s = SDL_SetVideoMode(200, 200, 32, SDL_HWSURFACE);
SDL_Rect rect = { 50, 50, 100, 100 };
SDL_FillRect(s, &rect, 0xffff0000);
printf("Done!\n");
return 0;
}
</code></pre>
<p>Compiled by Emscripten with:</p>
<pre><code class="bash" data-trim>
emcc -O2 test.c -o test.html
</code></pre>
</section>
<section>
<p>Which produces a default HTML harness:</p>
<iframe allowfullscreen style="background-color:white;" width="400" height="350" data-src="sdl-demo.html"></iframe>
</section>
<section>
<p>☃ In the future, import and call Web APIs directly from WebAssembly</p>
<ul>
<li class="fragment">Access DOM directly from C++/Rust</li>
<li class="fragment">Important for Web Frameworks using WebAssembly</li>
</ul>
</section>
<!---------------------------------------------------------------------------------- -->
<section>
<h2>Outline</h2>
<ul>
<li>What is WebAssembly? ✔</li>
<li>Short Tour of WebAssembly ✔</li>
<li>Accessing Web APIs from WebAssembly ✔</li>
<li>Beyond compiling C/C++</li>
<li>Frequently Asked Questions</li>
</ul>
</section>
<section>
<p>Currently, WebAssembly only has <em>linear memory</em></p>
<p class="fragment">Great if your language has a low-level memory model (C++, Rust, FORTRAN)</p>
<p class="fragment">But if your language has GC:</p>
<ul>
<li class="fragment">would need to implement/ship your own GC</li>
<li class="fragment">which misses optimizations in browser GC</li>
<li class="fragment">cannot collect cycles involving browser objects</li>
</ul>
</section>
<section>
<p>To provide first-class support for GC languages, WebAssembly needs direct GC access</p>
<p class="fragment">☃ Goal: add <em>low-level</em> GC primitives to avoid baking in one language's class model</p>
<p class="fragment">☃ Goal: share GC heap with JS, allow objects/strings/values to flow back and forth</p>
<p class="fragment">Follow on <a href="http://github.com/webassembly/gc">GitHub GC proposal repo</a></p>
</section>
<section>
<p>☃☃ So what could you do with GC support? ☃☃</p>
<ul>
<li class="fragment">TypeScript*</li>
<li class="fragment">
<div>
Typed functional programming + VDOM
<ul>
<li class="fragment">E.g.: Elm, Reason + React</li>
<li class="fragment">GC for functional code, linear memory for VDOM</li>
</ul>
</div>
</li>
</ul>
</section>
<section>
<p>Need even <em>more</em> features in WebAssembly to run dynamic languages <em>efficiently</em>:</p>
<ul class="snowmen-list">
<li>Code Patching</li>
<li>Fine-grained compilation</li>
<li><code>dynamic</code>/<code>any</code>-type</li>
</ul>
<p>Precedent with <code>invokedynamic</code> in the JVM</p>
<p class="fragment">☃☃ But this is all rather far off ☃☃</p>
</section>
<!---------------------------------------------------------------------------------- -->
<section>
<h2>Outline</h2>
<ul>
<li>What is WebAssembly? ✔</li>
<li>Short Tour of WebAssembly ✔</li>
<li>Accessing Web APIs from WebAssembly ✔</li>
<li>Beyond compiling C/C++ ✔</li>
<li>Frequently Asked Questions</li>
</ul>
</section>
<section>
<h2>Will WebAssembly Replace JS?</h2>
<p>No. Why?</p>
<ul>
<li>JS remains the privileged high-level language of the Web</li>
<li>JS has huge and growing momentum, vibrant ecosystem</li>
</ul>
<div class="fragment">
<p>In fact, WebAssembly may have quite the opposite effect:</p>
<p>
If you're going to target WebAssembly and your app needs a
scripting language, JS is a natural choice...
</p>
</div>
</section>
<section>
<h2>Compile JS to WebAssembly?</h2>
<p>Sure, if you want to go slower</p>
<ul>
<li>JS VMs do many low-level optimizations</li>
<li>WebAssembly needs a lot more capabilities to compete</li>
</ul>
<p class="fragment">...theoretically you could get a startup win by shipping your own bytecode + JS interpreter...</p>
</section>
<section>
<p>Find out more at <a href="http://webassembly.org">webassembly.org</a></p>
<p>
Lin Clark has an <em>awesome</em> <a href="https://hacks.mozilla.org/2017/02/a-cartoon-intro-to-webassembly/">blog post</a>
and <a href="https://www.youtube.com/watch?v=HktWin_LPf4">JSConf.eu talk</a> introducing WebAssembly
</p>
<p>
Slides at lukewagner.github.io/wasm-talk-2017
</p>
<div class="fragment">
<h2>Questions?</h2>
<a href="https://s3.amazonaws.com/mozilla-games/ZenGarden/EpicZenGarden.html">Background Eye Candy</a></a>
</div>
</section>
</div></div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
Reveal.initialize({
controls: false,
progress: false,
history: true,
center: true,
transition: 'fade',
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
]
});
</script>
</body>
</html>