News for hackers. Stuff that matters.
Re:io.js 1.4 released – featuring debuggable ES6 promises by _greim_ on Wednesday February 25, 2015 @03:54PM (#9109506)
So is the default use case this?

    process.on('unhandledRejection', function(ex){
      throw ex;
    });
...the idea being that it's analogous to an uncaught exception bubbling up to the top and causing the process to crash, which is generally what you want to happen?
Re:io.js 1.4 released – featuring debuggable ES6 promises by inglor on Wednesday February 25, 2015 @03:56PM (#9109523)
Yes, it's possible this indeed will be the default behavior at some later point.

Some people don't like this since `unhandledRejection`s can be handled later on at some point (for example, after a week of not adding a catch handler).

There is a discussion here: https://github.com/iojs/io.js/issues/830