Execute action functors by wrapping them in setTimeout.

[dashed]

Closes #22.

[dashed]

I put setTimeout as a dependency injection via utils.nextTick.

[spoike]

I'd rather avoid adding dependencies to the project (much like we did earlier with removing lodash as dependency). Even though nextTick is a small library, it seems unneccesary for the scope of our project.

I believe it's better in this case, for the sake of smaller footprint for browsers, to let the user choose to inject nextTick themselves through set nextTick and have setTimeout be the default implementation. Also add documentation on the README on how to inject nextTick.

[spoike]

Alternatively we could try to configure browserify to ignore the nextTick when building, and have Reflux use setTimeout default implementation if nextTick dependency is missing. Not sure how to do that though, I thought I saw some project doing this.

The goal is that the npm package should contain the nextTick package, while the bower component will have it optional.

[dashed]

I don't follow. The next-tick module is a polyfill for browsers, why would you want browserify to ignore it?

---

I amended the commit.

[spoike]

Because the user might be using the polyfill in their own build. No need to have it twice, once in their own project and second from our project. It's just unnecessary overhead.

[dashed]

Fine by me. Just leave it [the module] out.

[spoike]

All right!

[spoike]

I'll review the tests later tonight before merging.

[dashed]

Renamed all instances of nextTick to asap as inspired by:
https://github.com/kriskowal/asap
https://github.com/tildeio/rsvp.js/blob/master/lib/rsvp/asap.js
https://github.com/jakearchibald/es6-promise/blob/master/lib/promise/asap.js

[dashed]

Turns out asap, as a name, already means something different than what setTimeout does:
http://blog.izs.me/post/59142742143/designing-apis-for-asynchrony

---

The best option is a polyfilled setImmediate: https://github.com/YuzuJS/setImmediate

Reason: http://www.nczonline.net/blog/2013/07/09/the-case-for-setimmediate/

setTimeout is probably a decent shim, at least in chrome which takes care of its optimizations: https://code.google.com/p/chromium/issues/detail?id=146172#c10

Updated README on this.