News for hackers. Stuff that matters.
Re:ESLint 7.0 by tengbretson on Monday May 11, 2020 @03:13PM (#23145805)
I can't speak to the front-end, but there are plenty of situations in dealing with node where the correct thing to do is to throw a fatal error. If you have properly setup handlers for the end of the process lifecycle I don't see what the problem is.
Re:ESLint 7.0 by ergothus on Monday May 11, 2020 @03:27PM (#23145965)
But until recently an unhandled promise failure was NOT a thrown error, and when it is it's not the error you want.
Re:ESLint 7.0 by tengbretson on Monday May 11, 2020 @04:08PM (#23146402)
Absolutely! I guess what I'm trying to say is that in my experience, crashing on an unhandled rejection is a better remedy to the dangling promise problem than banning them outright.
Re:ESLint 7.0 by z3t4 on Monday May 11, 2020 @03:49PM (#23146188)
There is a saying - what you don't know can't hurt you. The idea of Promises comes from strongly typed static functional languages. Adding it to JavaScript was a terrible idea. Like with static modules - forcing the user to download the whole website/app before anything is rendered on the screen.
Re:ESLint 7.0 by aaomidi on Monday May 11, 2020 @05:24PM (#23147265)
Lol what are you on about.

You're mixing so many different things right now.