Feross Aboukhadijeh

We need `process.nextTick` for consistent async behavior. Read https://blog.izs.me/2013/08/designing-apis-for-asynchrony for more information. @jimmywarting What do you think about swapping all uses of `process.nextTick` with [`immediate`](https://github.com/calvinmetcalf/immediate) to resolve this issue?

> if you don't need it to be consistent and you can handle both scenarios then why bother using next tick or immediate at all? In my fork i just...

I assume this issue title was meant to say "background" not "foreground", right? I updated the title.

The solution that I'd like to propose here is to switch all `process.nextTick` calls across the codebase to `queueMicrotask`. This is a new API analogous to Node's `process.nextTick` but it...

If folks would like to start sending PRs to replace usage of `setTimeout(…, 0)` and `process.nextTick(…)`, I've sent a few to `simple-peer` and `simple-websocket` already, which you can use as...

@KayleePop Thanks for the PR :) > @KayleePop BTW, this problem goes away when async functions are used instead of callbacks Yep. I'd love to switch to a promise-based API...

> What to do about the torrent.js use of CHOKE_TIMEOUT as a delay? I don't believe this is related to this issue. The choke timeout is part of the normal...

I'd like to resume working on this issue to improve WebTorrent performance. We should replace all `process.nextTick` calls with [`queueMicrotask`](https://www.npmjs.com/package/queue-microtask) across all WebTorrent packages. Who wants to help send PRs...

This sounds like a bug that we should fix.

This feature seems interesting, but not high priority. We're already one of the fastest torrent clients out there. I'm skeptical that we need to prioritize based on geographic location when...