It's there a summary of why it's universally bad? We might need it for some kind of bytestorage API. Something mmap-like.
I'd like to see numbers. Promises were explicitly designed to allow for "fast forwarding" so that you don't need a full turn around the event loop. Might not be enough, but data matters.
-
-
(Am tied up packing for a big move but it sounded like others had numbers.) "Fast" depends on context. Overhead for an IO-bound event loop iteration is different from overhead for a small chunk of compute in it. We wouldn't push array lookups or object allocations into a promise.
-
I'd love to see data though. It's possible the APIs need a batch interface so you can hash multiple strings in one call if the per call overhead vs. computation cost is too high. Sync is not the only way to fix this.
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.