w/ a Worker + OffscreenCanvas you *must* yield execution back to the browser for drawing to actually render. There's no "commit" currently. e.g. you can't do a native-like blocking while loop and/or block with Atomics.wait()
-
Show this thread
-
I get some of the reasons why, but I think we need some way to do this inevitably, even if it comes with caveats. Not just for porting native apps (I care less about this) but to be able to performantly utilize multi-thread UI. More context:https://github.com/w3ctag/design-reviews/issues/288 …
1 reply 0 retweets 1 likeShow this thread -
This is just a hypothesis though. I could certainly be wrong! I'm gonna try an alternative that uses two Workers + Main thread + requestAnimationFrame and see where it leads.
1 reply 0 retweets 1 likeShow this thread
Replying to @_jayphelps
I'd love to see a codesandbox of what you're talking about...!
6:15 AM - 10 Oct 2019
0 replies
0 retweets
0 likes
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.