3 ms·
Some ideas in general: The article is about putting a framework & your Apps into a separate thread (calling this one App worker). Now, with SharedWorkers bein
by tobiu 6y ago
Some ideas in general:
The article is about putting a framework & your Apps into a separate thread (calling this one App worker).
Now, with SharedWorkers being fully supported, we can connect multiple main threads to a shared App worker. This way Apps live within the same realm and can directly communicate. They even share the virtual dom, leading to really great possibilities (moving dom nodes from one App to another).
E.g. if you would like to create a multi screen trading App, there is a big potential to speed up things.
On mobile this could also get interesting: imagine a native App with multiple WebViews. Those could as well share code and communicate directly.
Even in case there is just one browser window, the default worker setup (non shared workers) can make an impact.