@westbrook Maybe? That reminds me of #PartyTown and seems to be mirroring the entire set of #DOM APIs into a worker. IIRC #AMP doesn't actually have user #JavaScript at all.

I'm more thinking something like:

// my-component.js
function MyComponent() {
return <div>Hello, World!</div>;
}

Where the framework pushes this automatically into a web worker and then its rendering process would transfer the result to the main thread before rendering it.

// framework.js
const worker = new Worker('./my-component.js');
worker.postMessage('render');
worker.addEventListener('rendered', (evt) => {
const vdom = evt.detail.vdom;
diffAndApply(vdom, document.documentElement);
});

Where the framework forces all user code into the worker and handles the marshaling between the two, hiding the DOM altogether from user code.