Reading notes on 2016.4.4 ~ 2016.4.10

Pipeline is the future, not the C++

All callbacks scheduled via process.nextTick() are run at the end of a phase of the event loop (e.g. timers) before transitioning to the next phase. This creates the potential to unintentionally starve the event loop with recursive calls to process.nextTick().
“Pending callbacks” is where callbacks are queued to run that aren’t handled by any other phase (e.g. a callback passed to fs.write()).

setImmediate / setTimeout(0) -> fired off the event loop

nextTick -> fired immediately after the current code is done executing and BEFORE going back to the event loop

Looks cool!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.