News for hackers. Stuff that matters.
Re:Error Handling in Nodejs by bsimpson on Friday July 17, 2015 @07:05AM (#9902131)
This is a recent addition due to complaints like mine. Hopefully it becomes standard, because it's the way it should have always been.
Re:Error Handling in Nodejs by inglor on Friday July 17, 2015 @08:59AM (#9902484)
Well - the moral is to complain more, when I wrote and advocated for detection in io.js I needed people on my side - Domenic needs people to complain and help now for the browser spec - we're always a hand short :)
Re:Error Handling in Nodejs by esamatti on Friday July 17, 2015 @07:26AM (#9902200)
Wonder whether there is anything to add to the standard. Isn't this just a devtools issue?
Re:Error Handling in Nodejs by BonsaiDen on Friday July 17, 2015 @08:34AM (#9902387)
The standard should simply be changed to throw by default, but I guess the train has already left the station and so we're left with "bugs by design" before the spec has even been fully implemented by all vendors :(

But then again, in it's current "minimal" state of design, the Harmony Promises are inferior to any of the dedicated Promise A Plus implementations out there (e.g. Bluebird) and at least under Node there is little to no reason to use the built-in Promise object at this point in time.

Re:Error Handling in Nodejs by inglor on Friday July 17, 2015 @09:18AM (#9902554)