`setTimeout(fn, 0)` is a hack to defer calling `fn` til the synchronous stack has executed, and has many very useful applications — but there's a bit of cognitive overhead in ascertaining that `setTimeout` isn't being used as per its intended use case: this flummoxes novices especially, who may interpret this as a mistake. Is it worth abstractin…

later.js

// functions passed to later will only execute once the stack has resolved.
function later(fn){
  return setTimeout(fn,0);
}
 
void function executionScope(){
	var x = 0;
 
	console.log('Log 1: ' + x);
 
	++x;
 
	later(function(){
		console.log('Log 2: ' + x);
	});
 
	++x;
 
	console.log('Log 3: ' + x);
 
	++x;
}();