Re: IndexedDB, what were the issues? How do we stop it from happening again?

* Alex Russell wrote:
>My *first* approach to this annoyance would be to start adding some async
>primitives to the platform that don't suck so hard; e.g., Futures/Promises.
>Saying that you should do something does not imply that doubling up on API
>surface area for a corner-case is the right solution. was my
"first approach". Workers of course have it much easier, they just need
a single waiting primitive to make an asynchronous API synchronous. I've
argued against duplicating APIs for workers as proposed here, but so far
without much success, it would seem...
Björn Höhrmann · ·
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · 

Received on Friday, 15 March 2013 03:10:43 UTC