You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that the "way of doing async stuff" in JavaScript has significantly evolved in the past few years. We are moving to promises that empower the developers to make use of the async/await APIs.
With that, I truly think that callback APIs are slowing this process and making it more difficult.
Then I ask: Why is this library still uses callbacks to handle its async methods?
The text was updated successfully, but these errors were encountered:
I think that the "way of doing async stuff" in JavaScript has significantly evolved in the past few years. We are moving to promises that empower the developers to make use of the
async
/await
APIs.With that, I truly think that callback APIs are slowing this process and making it more difficult.
Then I ask: Why is this library still uses callbacks to handle its async methods?
The text was updated successfully, but these errors were encountered: