The curse of the never-ending async method call
Posted by: More Whidbey stuff,
on 17 Dec 2014 |
View original | Bookmarked: 0 time(s)
Whether you use promises, callbacks, or other abstractions (except maybe the async/await pattern) to deal with asynchrony, control flow is going to get harder to follow. Stack traces are typically meaningless, and finding what went wrong can take substantially more time. One thing that very often goes wrong, especially during development, is when an asynchronous method never calls back. It may be because a service never answers, or because theres a bug in the code that causes the callback to never...