probably never. using libs gives consistency across runtimes and allows to patch behavior if necessary.
-
-
-
when does that end? Do you use userspace arrays? Maps? Avoid new Date()?
-
arrays and new maps cannot be expressed as libraries. but such things as fetch can and probably should.
-
Map can definitely be expressed as a library.
-
well, this just to programmer pragmatism. with browser promises we will still carry polyfills => more complicated witout benifit.
-
standard promises have to exist because async APIs have to return something.
-
the only promise-d api i know is fetch. and it's redundant. with CBs it was so simple - u use promises in applogic, cb in api calls
-
standard callback patterns are not intrinsically simpler than promises and more error prone (ever seen a cb run twice? I have)
- 10 more replies
New conversation -
-
-
...were the default in Ember apps. :)
@wycats -
you can still write Promise.all etc in Ember no?
-
RSVP.Promise in Ember doesn't resolve as a microtask. So I wonder what timing bugs will be revealed by switching.
-
yeah there are real timing questions. Wish for hooks. /cc
@IgorMinar -
would be nice if we could inspect sync from the template layer
-
strong confirm.
@domenic expressed support this week. Let's do it. -
ya we spoke about it in the past. The key is benchmarks and real world demonstrations
-
I the main frameworks are all coalescing along the "single flush render for perf" story
- 10 more replies
New conversation -
-
-
* were cancelable * accepted callbacks & transmuted them to promises to ease transition of legacy code * had well-defined semantics
-
promises don't have well-defined semantics?
-
and I assume you mean "accepted a node-style, error-first, callback-taking function"?
-
yes, though I'd probably feel fine with using a library for this too in some interim period
End of conversation
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.