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
Actually I think async does come back to block the main thread after it has reached its turn. So just for the sake of OCD there’s 2 options:
Fork a worker, but only a large enough JSON will benefit, in terms of freeing up the main thread. Otherwise it’s okay to live with a very brief period of blocking. Also when a worker posts the message, the main thread still needs to synchronously serialise. It’s possible to encode in the worker to Unint8array, then in the main thread, use a Coroutines parser.
use coroutines for transforming objects in the main thread.
if it's still using the main thread despite being made to run asynchronously, isn't it just the same as synchronous execution?
if so should you employ workers?
The text was updated successfully, but these errors were encountered: