Hi floodfx, we should chat at some point if you're on slack/discord/etc. I'm building something extremely similar and there's potential opportunity to share some code/learnings. Personally I feel this design paradigm is the real web 3.0.<p>My project is <a href="https://diffhtml.org/" rel="nofollow">https://diffhtml.org/</a> and I have started experimenting with middleware to bridge to server and client workers: <a href="https://github.com/tbranyen/diffhtml/pull/251" rel="nofollow">https://github.com/tbranyen/diffhtml/pull/251</a>. For the server worker, it uses a WebSocket to ferry the VDOM diff patches, custom events, and property access/function calls. A big goal is to allow synchronous "main thread" access from workers, including on the server-side. This would allow you to write your UI code as if you were a client side app. It does this the same way as partytown using a SharedArrayBuffer and Atomics. You can see demo source code here: <a href="https://gist.github.com/tbranyen/2f5be81cfb7b3aa1bb443c8ef13f43a4" rel="nofollow">https://gist.github.com/tbranyen/2f5be81cfb7b3aa1bb443c8ef13...</a>.<p>I've also toyed around with hot reloading components without the need for a pre-processor like Babel, and the results are hugely promising. Stateful live UI updates from saving a component file to seeing in the browser without all the fuss with complex build steps is liberating.<p>I'm probably a few months out from having a usable beta, but I'm going to follow your project closely. Thanks for sharing!