Asynchronous Adventures in Javascript by Benjamin Diaguid

A really, really _nice_ detailed but understandable discussion of the whys and whats and hows and wheres of asynchronous Javascript code, which has previously been to me nothing but dark magical arts:

1. Understanding the Event Loop: https://medium.com/dailyjs/asynchronous-adventures-in-javascript-understanding-the-event-loop-fc6f968d5f72
2. Callbacks: https://medium.com/dailyjs/asynchronous-adventures-in-javascript-callbacks-39880f1b470e
3. Promises: https://medium.com/dailyjs/asynchronous-adventures-in-javascript-promises-1e0da27a3b4
4. Generators: https://medium.com/dailyjs/asynchronous-adventures-in-javascript-generators-74199218bab2
5. Async/Await: https://medium.com/dailyjs/asynchronous-adventures-in-javascript-async-await-bd2e62f37ffd

The above gives me courage to have another crack at chapter [17](http://eloquentjavascript.net/17_http.html) of "Eloquent Javascript", since I now have more _context_ and _googable_ terms.

'@nelsonic I think you might find the discussion on callbacks useful for your "Elm Architecture in Javascript" tutorial, given that it was assumed the audience might not be familiar with the callback pattern. I myself was aware of delayed evaluation from functional Programming ([thunk](https://en.wikipedia.org/wiki/Thunk)) but did not quite connect the concept of delayed evaluation with asychronicity, so I get two apples for the price of one!: oh, it is called a callback becauses the function will be called later, depending on whether it has finished its work, or is just needed right now!

Überprüfe die fünf verlinkten Artikel über event loop, callbacks, promises, generators und async/await sowie die Verweise auf Kapitel 17 von Eloquent JavaScript und das Tutorial zur Elm Architecture. Das Issue nennt weder eine Repository-Datei noch eine konkrete Änderung. Bestätige daher die beabsichtigte Aktualisierung der Dokumentation, bevor du definierst, was „erledigt“ bedeutet.

Vom Indexierungsmodell aus dem Issue-Text verfasst.