I bet Promise people will start using async / await for sync operations, fully not realizing that it'll take away any reasoning about code
-
-
Replying to @yoshuawuyts
If sync and async ops look the same, code that touches IO becomes indistinguishable from the rest - which means optimizing becomes harder
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
The general approach to creating more efficient services is: 1. reduce IO, 2. do concurrency; if either becomes harder it's bad for perf
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
With callbacks it's apparent which parts do IO, and which parts don't. If it's a callback, it's doing IO (or working around JSON.parse :/)
1 reply 1 retweet 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts it's a convention to not use callbacks in synchronous operations, you can't know for sure just looking at the interface1 reply 0 retweets 0 likes
@a0viedo but yeah, you can be pretty sure with some authors - I pretty much only use code from people I trust, and they stick to conventions
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.