-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
executable file
·705 lines (588 loc) · 30.6 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>bitHound</title>
<meta name="description" content="">
<meta name="author" content="bitHound">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<link rel="icon" href="img/symbol_colour.png" type="image/x-icon">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="css/reveal.min.css">
<link rel="stylesheet" href="css/theme/bithound.css" id="theme">
<!-- For syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- If the query includes 'print-pdf', use the PDF print sheet -->
<script>
document.write( '<link rel="stylesheet" href="css/print/' + ( window.location.search.match( /print-pdf/gi ) ? 'pdf' : 'paper' ) + '.css" type="text/css" media="print">' );
</script>
<script src="http://localhost:35729/livereload.js?snipver=1"></script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section class="main-title" data-background="img/symbol_reversed.svg" data-background-size="150%">
<img src="img/fulllogo_reversed.svg" class="simple-img full-logo" />
<h3>Why would we ever build a distributed computing platform in Node?</h3>
<p>
<small>Presented by Gord Tanner</small><br />
<a href="https://www.bithound.io">www.bithound.io</a> / <a href="http://twitter.com/bithoundio">@bithoundio</a>
</p>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Who am I?</h2>
<h3><a href="https://www.bithound.io">www.bithound.io</a></h3>
<br>
Gord Tanner (<a href="http://twitter.com/gordtanner">@gordtanner</a>)
<br>
Co Founder / CTO
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h3>Founding Team</h3>
<img src="img/team.jpg" alt="">
<a href="http://www.communitech.ca/main-communitech/view-from-the-loo-bithound-house-builds-on-downtown-momentum/#.VNTzk8Z-9TY">http://www.communitech.ca/main-communitech/view-from-the-loo-bithound-house-builds-on-downtown-momentum/#.VNTzk8Z-9TY</a>
<aside class="notes">
<pre>
Dan, PJ and myself
Kitchener Waterloo ontario Canada
Old restored house in the downtown core.
</pre>
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>What do we do?</h2>
<p>Code quality, maintainability, and stability for all of your public and private project repositories.
</p>
<img src="img/commit-graph.png" alt="">
<br />
<a href="https://www.bithound.io">www.bitHound.io</a>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Problem:</h2>
<pre>
> time jshint .
---------------------
(lots of errors here)
---------------------
7368 errors
real 0m29.321s
user 0m28.627s
sys 0m0.508s
</pre>
<h5 style="text-align: left;">- Do this for 1K+ commits in a project</h5>
<h5 style="text-align: left;">- There are many more things to look at</h5>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Waiting sucks</h2>
<img src="img/waiting.jpg" alt="" />
<aside class="notes">
We knew from day 1 this was a concurrent problem
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h1>concurrency</h1>
In computer science, concurrency is a property of systems in which several <i style="color: red">computations are executing simultaneously</i>,
and <i style="color: red;">potentially interacting</i> with each other. The computations may be executing on multiple cores in the same chip, preemptively time-shared threads on the same processor, or executed on physically separated processors.
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Why JavaScript?</h2>
<img width="50%" src="img/gopherbw.png" alt="">
<aside class="notes">
<ul>
<li>go: coroutines</li>
<li>c#, java</li>
<li>ruby, python</li>
</ul>
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/tinyhippos.png" alt="" width="60%" />
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/ripple.png" alt="">
<a href="https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphabnejjhdalkjhgipohgpdnoc?hl=en">https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphabnejjhdalkjhgipohgpdnoc?hl=en</a>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/github-javascript.png" alt="">
<h3>is</h3>
<img width="50%" src="img/fulllogo_reversed.svg" alt="">
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h1>concurrency</h1>
In computer science, concurrency is a property of systems in which several computations are executing simultaneously,
and potentially interacting with each other.
The computations may be executing on <i style="color: red">multiple cores</i> in the same chip,
preemptively <i style="color: red;">time-shared threads</i> on the same processor,
or executed on physically <i style="color: red;">separated processors</i>.
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Shared Memory</h2>
Concurrent components communicate by <i style="color: red;">altering</i> the contents
of <i style="color: red;">shared memory</i> locations (exemplified by Java and C#). This style of concurrent programming
usually requires the application of <i style="color: red;">some form of locking</i>
(e.g., mutexes, semaphores, or monitors) to coordinate between threads.
A program that properly implements any of these is said to be
<i style="color: red;">thread-safe </i>.
<small>
<a href="http://en.wikipedia.org/wiki/Concurrent_computing">http://en.wikipedia.org/wiki/Concurrent_computing</a>
</small>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Message Passing</h2>
Concurrent components communicate by <i style="color: red;">exchanging messages</i>
(exemplified by Scala, Erlang and occam). The exchange of messages may
be carried out <i style="color: red;">asynchronously</i>, or may use a <i style="color: red;">synchronous</i> "rendezvous" style
in which the sender blocks until the message is received.
Asynchronous message passing may be <i style="color: red;">reliable or unreliable</i>
(sometimes referred to as "send and pray"). Message-passing concurrency
tends to be far easier to reason about than shared-memory concurrency, and is typically considered a more robust form of concurrent programming.
<br/>
<small>
<a href="http://en.wikipedia.org/wiki/Concurrent_computing">http://en.wikipedia.org/wiki/Concurrent_computing</a>
</small>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<b>
Node is a platform for easily building fast, <i style="color: red;">scalable network applications. </i>
Node uses an event-driven, non-blocking I/O model that makes it lightweight and efficient,
perfect for <i style="color: red;">data-intensive</i> real-time applications that run across <i style="color: red;">distributed devices</i>.
</b>
<br />
<small><a href="http://nodejs.org/">http://nodejs.org/</a></small>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h3>The cost of I/O</h3>
<pre style="font-size: 1em;">
L1-cache 3 cycles
L2-cache 14 cycles
RAM 250 cycles
Disk 41 000 000 cycles
Network 240 000 000 cycles
</pre>
<a href="http://blog.mixu.net/2011/02/01/understanding-the-node-js-event-loop/">http://blog.mixu.net/2011/02/01/understanding-the-node-js-event-loop/</a>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Async IO</h2>
<img src="img/event-loop.jpg" alt="">
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
function fibonacci(n) {
if (n < 2)
return 1;
else
return fibonacci(n-2) + fibonacci(n-1);
}
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end(fibonacci(40));
}).listen(1337, "127.0.0.1");
</pre>
<a href="https://www.semitwist.com/mirror/node-js-is-cancer.html">https://www.semitwist.com/mirror/node-js-is-cancer.html</a>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Am i going to "create" another distributed framework?</h2>
<img src="img/npm.png" alt="">
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/no.gif" alt="">
<p>"this is a very personal choice"</p>
<a href="https://github.com/bithound/farm.bithound.io">https://github.com/bithound/farm.bithound.io</a>
<aside class="notes">
It is a very personal choice, choose the tools that work for you, the network design that
works for you.
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/zeromq.png" alt="" />
<blockquote>ØMQ looks like an embeddable networking library but acts like a concurrency framework.</blockquote>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
.------------. .--------------.
| | | |
| TCP socket +------->| | ZAP!
| | BOOM! | 0MQ socket |
'------------' | | POW!!
^ ^ ^ | |
| | | '--------------'
| | |
| | |
| | '--------- Spandex
| |
| '-------------- Cosmic rays
Illegal radioisotopes from
secret Soviet atomic city
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Sockets that carry <i style='color: red;'>atomic messages</i> across various <i style='color: red;'>transports</i> like:</h2>
<ul>
<li>in-process</li>
<li>inter-process (shared memory)</li>
<li>TCP</li>
<li>multicast</li>
</ul>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>You can <i style='color: red'>connect</i> sockets <i style='color: red;'>N-to-N</i> with patterns like</h2>
<ul>
<li>fan-out, fan-in</li>
<li>publish-subscribe</li>
<li>task distribution</li>
<li>request-reply</li>
</ul>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Tasks</h2>
<img src="img/mission.png" alt="">
<aside class="notes">
<ul>
<li>Think of the atomic chunks of work in your app</li>
<li>You are probably wrong</li>
</ul>
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<ul>
<li>understand your project</li>
<li>assess your applications needs</li>
<li>only then define your tasks</li>
</ul>
<aside class="notes">
Build in a way that you can adapt.
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Roles</h2>
<pre>
.------------. .------------.
| | | |
| MASTER | | SLAVE |
| | | |
.------------. .------------.
- starts jobs - works on jobs
- breaks down work
- listens to status
</pre>
<aside class="notes">
Master = web app
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
.------------. Hey, can you do this thing for me? .------------.
| |------------------------------------>| |
| MASTER | Sure! here you go buddy | SLAVE |
| |<------------------------------------| |
'------------' '------------'
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
.------------.
.------------.|
.------------.||
.------------. here are a bunch of things to do! .------------.|||
| |------------------------------------>| |||'
| MASTER | Sure! here you go buddy | SLAVE ||'
| |<------------------------------------| |'
'------------' '------------'
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
.--------. do this! .-------. thats a lot of work! .-------.
| |------------->| | can you help me? | |
| MASTER | here you go | SLAVE |--------------------->| SLAVE |
| |<-------------| |<---------------------| |
'--------' '-------' '-------'
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
.what is the difference?.
| |
V V
.--------. do this! .-------. thats a lot of work! .-------.
| |------------->| | can you help me? | |
| MASTER | here you go | SLAVE |--------------------->| SLAVE |
| |<-------------| |<---------------------| |
'--------' '-------' '-------'
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h3>There is no difference</h3>
<pre>
.--------. do this! .--------. thats a lot of work! .--------.
| |------------->| | can you help me? | |
| WORKER | here you go | WORKER |--------------------->| WORKER |
| |<-------------| |<---------------------| |
'--------' '--------' '--------'
</pre>
<aside class="notes">
Except some people jsut want to tell others to do work and not work themselves (ie our webserver)
</aside>
</section>
<section data-transition="none" data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
<span style="color: red;margin: 0;padding: 0;">var farm = require('farm');</span>
// I need someone to do something for me
var task = {};
farm.jobs.send(task, function (err, result) { });
// I have a bunch stuff people can work on for me
var jobs = [j1, j2, j3, j4, .....];
farm.jobs.distribute(tasks, function (err, result) { });
// global cluster pub / sub
farm.events.publish('new_sha', {sha: '', owner: '', repo: ''});
farm.events.subscribe('new_sha', function (event) { });
farm.worker(function (task, callback) {
//do stuff
callback(err, result);
});
</pre>
</section>
<section data-transition="none" data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
var farm = require('farm');
<span style="color: red; margin: 0;padding: 0;"> // I need someone to do something for me
var task = {};
farm.jobs.send(task, function (err, result) { });</span>
// I have a bunch stuff people can work on for me
var jobs = [j1, j2, j3, j4, .....];
farm.jobs.distribute(tasks, function (err, result) { });
// global cluster pub / sub
farm.events.publish('new_sha', {sha: '', owner: '', repo: ''});
farm.events.subscribe('new_sha', function (event) { });
farm.worker(function (task, callback) {
//do stuff
callback(err, result);
});
</pre>
</section>
<section data-transition="none" data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
var farm = require('farm');
// I need someone to do something for me
var task = {};
farm.jobs.send(task, function (err, result) { });
<span style="color: red;">// I have a bunch stuff people can work on for me
var jobs = [j1, j2, j3, j4, .....];
farm.jobs.distribute(tasks, function (err, result) { });</span>
// global cluster pub / sub
farm.events.publish('new_sha', {sha: '', owner: '', repo: ''});
farm.events.subscribe('new_sha', function (event) { });
farm.worker(function (task, callback) {
//do stuff
callback(err, result);
});
</pre>
</section>
<section data-transition="none" data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
var farm = require('farm');
// I need someone to do something for me
var task = {};
farm.jobs.send(task, function (err, result) { });
// I have a bunch stuff people can work on for me
var jobs = [j1, j2, j3, j4, .....];
farm.jobs.distribute(tasks, function (err, result) { });
<span style="color: red;">// global cluster pub / sub
farm.events.publish('new_sha', {sha: '', owner: '', repo: ''});
farm.events.subscribe('new_sha', function (event) { });</span>
farm.worker(function (task, callback) {
//do stuff
callback(err, result);
});
</pre>
</section>
<section data-transition="none" data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<pre>
var farm = require('farm');
// I need someone to do something for me
var task = {};
farm.jobs.send(task, function (err, result) { });
// I have a bunch stuff people can work on for me
var jobs = [j1, j2, j3, j4, .....];
farm.jobs.distribute(tasks, function (err, result) { });
// global cluster pub / sub
farm.events.publish('new_sha', {sha: '', owner: '', repo: ''});
farm.events.subscribe('new_sha', function (event) { });
<span style="color: red;">farm.worker(function (task, callback) {
//do stuff
callback(err, result);
});</span>
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Launch Day!</h2>
<img width="50%" src="img/twilight.png" alt="">
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>what works on one machine well, doesn't always work as well on 200 machines</h2>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Dev Env (on OSX)</h2>
<pre>
#-------------#
| |
| WEB APP |
| |
'-------------'
|
v
.------------.
| |
| BROKER |
| |
#------------#
|
v
.------------.
| |
| WORKER |
| |
#------------#
</pre>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Prod Env</h2>
<pre>
#-------------#
| |
| WEB APP |
| |
'-------------'
|
v
.------------.
| |
| BROKER |
| |
#------------#
|
.------------.
| 100s OF |
| BOXES |
'------------'
|
.---------------+---------------.
| | |
v v v
.------------. .------------. .------------.
| | | | | |
| WORKER | | WORKER | | WORKER |
| | | | | |
#------------# #------------# #------------#
</pre>
<aside class="notes">
<ul>
<li>100s of boxes that didn't talk to each other</li>
<li>100s of boxes that tried to all clone at the same time</li>
<li>all of our "sharing" code assumptions were wrong</li>
</ul>
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/vagrant.png" alt="">
<a href="https://www.vagrantup.com/">https://www.vagrantup.com/</a>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/vagrant_status.png" alt="">
<p><b style="color: red;">PROTIP:</b> If you are developing a distributed application, you should work in a distributed environment</p>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/cattle.png" alt="">
<h2>Pets or Cattle?</h2>
<aside class="notes">
<ul>
<li>Services</li>
<li>Computers</li>
<li>Jobs</li>
</ul>
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<img src="img/failure-option.jpg" alt="">
<aside class="notes">
You should expect things to fail. If something fails, just try again. Schedule for it to run later or try right away.
If it keeps failing then you can look into it.
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>Rube Goldberg Machine</h2>
<img src="img/cli.png" width="40%" alt="">
<aside class="notes">
UNIX WAY.
Develop a series of tools that can be chained together and run atomically
</aside>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>You are the one</h2>
<img src="img/machine.gif" alt="">
<small>"The function of the One is now to return to the Source allowing a temporary dissimination of the code you carry reinserting the Prime Program." - The Architect</small>
</section>
<section data-background="img/symbol_reversed.svg" data-background-size="70%" data-background-position="120%">
<h2>So why node?</h2>
<img src="img/glue.gif" alt="">
<aside class="notes">
<ul>
<li>Async IO and simple concurrency</li>
<li> it was an amazing languages to quickly glue a wide array of tools and programs together. </li>
<li>command line integration was awesome</li>
</ul>
</aside>
</section>
<section class="main-title" data-background="img/symbol_reversed.svg" data-background-size="150%">
<img src="img/fulllogo_reversed.svg" class="simple-img full-logo" />
<h2>Thank you!</h2>
<h3><a href="https://www.bithound.io">www.bithound.io</a></h3>
<ul>
<li>Gord Tanner (<a href="http://twitter.com/gordtanner">@gordtanner</a>)</li>
<li><a href="http://bithound.github.io/2015-NodeSummit/">http://bithound.github.io/2015-NodeSummit/</a></li>
</ul>
</br>
</br>
<p>
<small><a href="https://www.bithound.io">www.bithound.io</a> / <a href="http://twitter.com/bithoundio">@bithoundio</a></small>
</p>
</section>
</div>
</div>
<div class="footer">
<!--<img src="img/wordmark_grey_reversed.svg" class="simple-img wordmark" />-->
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.min.js"></script>
<script>
// Full list of configuration options available here:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
theme: Reveal.getQueryHash().theme, // available themes are in /css/theme
transition: Reveal.getQueryHash().transition || 'default', // default/cube/page/concave/zoom/linear/fade/none
// Parallax scrolling
// parallaxBackgroundImage: 'https://s3.amazonaws.com/hakim-static/reveal-js/reveal-parallax-1.jpg',
// parallaxBackgroundSize: '2100px 900px',
// Optional libraries used to extend on reveal.js
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true, condition: function() { return !!document.body.classList; } },
{ src: 'plugin/notes/notes.js', async: true, condition: function() { return !!document.body.classList; } }
]
});
</script>
<!-- Live reload -->
</body>
</html>