Tim Kevin Oxley

@sindresorhus this setup is arguably better than the spec :(

@sindresorhus Spec `AggregateError` displays ok in node because it also prints the error's own properties via `util.inspect`, but `errors` are entirely hidden in the browser console using `console.log` or `console.error`:...

@parro-it @loopmode This question was recently discussed on twitter by v8 team member @bmeurer: * https://twitter.com/bmeurer/status/987563203919048705 * https://twitter.com/bmeurer/status/987582050692628481

Perhaps just the driver with some more contrast would do the trick:   

Hm, this isn't what I was thinking at all. That switch you propose is messy. This is what I was thinking: server.on('listening', function() { }) server.on('close', function() { }); server.on('error',...

I was thinking something along the lines of `xmlrpc-protocol`, simply because the original idea for the separation was inspired by https://github.com/substack/dnode-protocol#readme. Ideally, you'd provide a streaming interface and a simple...

If that snippet library was merged, I'd like to see and the overlapping functions (eg foreeach/func) removed, as well as the non-core module snippets (eg for mongoose/sockeio)

A similar idea (with no code as afaik): http://nodeos.github.io/. Kinda pretty website though.

Not even sure if chrome implementation is valid, i.e. are you supposed to be able to attach catch handlers asynchronously?

bump