on node, this can actually be very difficult or even impossible if using 3rd party libraries.
For example, some node internals like networking require the invoker to attach to some obscure .on("error") event to avoid uncaught errors. and a lot of the time these 3rd parties are not aware of it.
I'm all for deno being built from the ground up to properly crash on uncaught errors. Silent ignoring is a really stupid decision.
I never understood why this is necessary. Using promises means you get to use try-with-resources style construct for handling non-memory resources safely. As such you no longer need to crash on uncaught errors, except errors pertaining to resource disposal.
i think the reason is that, in my example of networking, the network i/o is an "interupt" kind of event, that is triggered outside of normal execution. like if there's a socket timeout.
probably didn't have to be designed this way, but it was designed pre-promises and I guess they are lothe to change it.
