-
-
Replying to @robotlolita
@notSorella I don't get it. I show both how there's not much added complexity to adoption and real wins.@polotek2 replies 0 retweets 0 likes -
Replying to @robotlolita
@notSorella the chaining example is a syntactic improvement. Error handling is nicer than domains.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@notSorella domains do more complex error handling then promises. Sockets and error emitters are complex. setTimeout is complex1 reply 0 retweets 0 likes -
Replying to @Raynos1 reply 0 retweets 0 likes
-
Replying to @robotlolita
@notSorella@wycats setTimeout is outside of a promises error handling flow. it's inside the domain's error handling flow.1 reply 0 retweets 0 likes -
Replying to @Raynos
@Raynos@notsorella@wycats with ptomises you dont write setTimeout, you write wait(n).then(...) which will go through promise error flow1 reply 0 retweets 0 likes -
Replying to @gozala
@gozala@notSorella@wycats that assumes all third party code is nice and uses promises & not setTimeouts. Domains handle it.1 reply 0 retweets 0 likes -
Replying to @Raynos
@Raynos@notsorella@wycats if node chose promises over domains that wouldn't be an issue.3 replies 0 retweets 0 likes
@gozala reading abt domains, looks like domains still have uses with promises, but mostly about slurping ambient errors @Raynos @notSorella
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.