Not always async demo added.

Author: JaimeSalas

07 Timer Gotchas/README.md

@@ -85,4 +85,3 @@
 
 * If we change `requestDelay` to `10`, the avarage gets closer to `10ms`. The reason that this is happen is because by default the browser will set a value close to 4 by default.
 
-* El delay lo inicializamos a 0, cuando lo ejecutamos, estamos pidiendo un delay de 0, pero en el avarage llega cerca de los 5 ms. Lo cambiamos a 10 ms. y la media de resultado que nos da es mucho más proxima a 10ms. La razón de que ocurra esto, es que cuando nosotros ponemos 10 ms, el navegador lo va a modificar para que sean 4ms.

08 Not always async/README.md

@@ -0,0 +1,25 @@
+## Challange ¿Cuantos pequeños programas?
+* Folder structure:
+
+08 Not Always Async/
+├── src/
+│   ├── content/
+|   |   ├── site.css
+│   ├── js/
+|   |   ├── utils.js
+|   |   ├── main.js
+│   ├── index.html
+│   └── bootstrap-theme.min.css
+├── gulpfile.js
+├── package.json
+
+## Steps.
+
+### 1. Open `main.js`.
+
+* Challange -> How many little programs? // 1
+* What it's going to be show up on console? // 2, 4, 6
+
+* We can ask ourselves if this function is an async function or not. The fact is that there is no way to know it, without know how `forEach` function is implemented.
+
+* We can wrap the function with `setTimeout`, and we obtain another thing.

08 Not always async/gulpfile.js

@@ -0,0 +1,24 @@
+'use strict';
+
+const gulp = require('gulp'),
+  connect = require('gulp-connect'),
+  open = require('gulp-open'),
+  options = {
+    port: 9005,
+    root: ['src'],
+    devBase: 'http://localhost:',
+    browsers: ['safari', 'chrome']
+  },
+  openOptions = {
+    uri: options.devBase + options.port,
+    app: options.browser
+  };
+
+  gulp.task('connect', () => connect.server({
+    root: options.root,
+    port: options.port
+  }));
+  // https://github.com/stevelacy/gulp-open/issues/15
+  gulp.task('open', () => gulp.src(__filename).pipe(open(openOptions)));
+
+gulp.task('default', ['connect', 'open']);