You should use iterator methods for clarity and fewer side effects.
Proposal for The O'Reilly Software Architecture Conference 2015
Test live application by mocking responses without modifying code or installing plugins.
Which keys are expensive in a collection of objects?
Feeding fake variables to a function taken out of its lexical scope.
Plus easy promise chaining using Ramda.
Make a presentation about your life a couple of weeks after joining the company.
Measuring how close a library follows semver semantics when publishing new releases.
Implementing Todo list with Undo using immutable data structure.
Eliminate variables and functions via flexible selective application.
Functor + Applicative = Applier
Plot data right inside Chrome DevTools while debugging.
Semi-private data common to link and controller without adding to the scope.
Functor Promise together with Maybe applicative.
Test function for purity using lexical scope and runtime context.
Prepare for future async data flow by wrapping primitives in promises.
Limit dirty checking to the given scope when reacting to user events.
Check if your current module breaks other modules before publishing.