Discuss
  • Message History
John Barton (2013-11-13T15:33:26.000Z)
On Tue, Nov 12, 2013 at 8:07 PM, David Bruant <bruant.d at gmail.com> wrote:

> Le 12/11/2013 13:42, Kris Kowal a écrit :
>
>  One of the concerns with promises is that they consume exceptions that
>> may or may not be handled.
>
>  ...

> I understand the need to know when a promise has an unhandled error at
> development time, I'm less clear on why you need to know it at runtime. Why
> would you do with this information? handle the error?
> If you think of wrapping promises in weakrefs, why not just add error
> handling?
> To me, it looks like the same amount of effort.


Kris and David highlight a critical issue for using promises in
professional applications: changes to source, including eg library version
changes, lead to failures that are not detected at development time and
thus ship to users where they are (um) exceptionally difficult to sort out.
I don't understand why this issue isn't a show stopper for systemic
promises proposals.

jjb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131113/6a6219b5/attachment.html>
domenic at domenicdenicola.com (2013-11-17T18:01:42.317Z)
On Tue, Nov 12, 2013 at 8:07 PM, David Bruant <bruant.d at gmail.com> wrote:

> Le 12/11/2013 13:42, Kris Kowal a écrit :
>
>>  One of the concerns with promises is that they consume exceptions that
>> may or may not be handled.
>
>  ...
> I understand the need to know when a promise has an unhandled error at
> development time, I'm less clear on why you need to know it at runtime. Why
> would you do with this information? handle the error?
> If you think of wrapping promises in weakrefs, why not just add error
> handling?
> To me, it looks like the same amount of effort.


Kris and David highlight a critical issue for using promises in
professional applications: changes to source, including eg library version
changes, lead to failures that are not detected at development time and
thus ship to users where they are (um) exceptionally difficult to sort out.
I don't understand why this issue isn't a show stopper for systemic
promises proposals.
Edit