webworker experiment idea
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I'm a bit constrained on time, so posting it here if anyone wants to dabble in some mad science.
virtual-dom can be rendered safely in a WebWorker because it produces a patch that is serializable as a string. yo-yo creates DOM nodes through require('global') that are diffed against the DOM. Webworkers only allow messages to be passed that can be parsed by the structured clone algorithm.
Now the experiment would be: can we create a DOM tree / diff from within a webworker, and apply it on the DOM in the main thread? Do we need an intermediary state or do require('global') nodes work for that? Also: what are the perf implications if we manage to get it to work?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file or test to modify. Start by reading the virtual-dom and yo-yo rendering paths, then check how require('global') nodes and WebWorker messages interact with the structured clone algorithm. Define a minimal worker experiment and a way to compare its performance with the existing main-thread rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100