@brianleroux Think Iโm going off https://t.co/B4C7SQitoF
> Something that the algorithm above doesnโt spell out explicitly is the fact that serialization blocks the sending realm, while deserialization blocks the receiving realm.
@brianleroux Huh, Iโve always been under the impression that postMessage + structured clone still requires (blocking) deserialization on the main thread.
@brianleroux Neat post! Iโm confused about the worker bit:
> Updating data may require fetching data from the server, which can be slow. If we can offload this slow work somewhere we can avoid stalling the interactivity of the UI
This should be mostly async except the JSON parse?
@zeeg Is a similar vein, would be neat if Sentry could try and replicate bugs the SDK already found by inferring a userโs trail via breadcrumbs (guessing theyโre too lossy, but would be cool)
@zeeg Curious what the MITM role was (passive traffic collection for learning flows? Replaying requests for instrumented clients without hitting real server later)?
Just got laid off from my job - if anyone is hiring Senior Software Engineers please reach out. I'm fluent in Javascript, Typescript, React, Apollo GraphQL.
Would love to add to your team, or help get something off the ground! #OpenToWork