Anne van Kesteren (2013-07-17T20:40:50.000Z)
On Wed, Jul 17, 2013 at 1:04 PM, Rick Waldron <waldron.rick at gmail.com> wrote:
> Can you explain why startDate was specified was a Date object?

Because that's how JavaScript represents time? Event.timeStamp was
supposed to be a Date object too:
http://www.w3.org/TR/DOM-Level-2-Events/ecma-script-binding.html Not
sure why it was not implemented that way.

I don't really follow your line of reasoning. Existing APIs use a mix
of callbacks and events. Should we not switch to promises where we
can, but rather stick with precedent?


--
http://annevankesteren.nl/
domenic at domenicdenicola.com (2013-07-24T00:36:59.463Z)
On Wed, Jul 17, 2013 at 1:04 PM, Rick Waldron <waldron.rick at gmail.com> wrote:
> Can you explain why startDate was specified was a Date object?

Because that's how JavaScript represents time? Event.timeStamp was
supposed to be a Date object too:
http://www.w3.org/TR/DOM-Level-2-Events/ecma-script-binding.html Not
sure why it was not implemented that way.

I don't really follow your line of reasoning. Existing APIs use a mix
of callbacks and events. Should we not switch to promises where we
can, but rather stick with precedent?