[elm-discuss] Re: Web worker possibility? Perf concerns.
Hey thanks for the reply. I'd searched the wrong Elm group before posting about the topic. I see what you mean though :) -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[elm-discuss] Re: Web worker possibility? Perf concerns.
Or. It could of course be done. But neither React nor virtual-dom (which elm uses) works that way today. Chances are they won't support this any time soon either. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[elm-discuss] Re: Web worker possibility? Perf concerns.
No, this won't work. 1. Webworkers cannot update the GUI, this has to be done on the UI "thread". 2. Webworkers do not share memory (not yet anyway). Which means you would need to copy the UI tree between worker and main loop. 3. Hundreds of thousands of nodes will be slow to copy between workers. That being said. Why do you have "hundreds of thousands of nodes" in the UI? Elm can be sufficiently faster than React out of the box (due to immutable datastructures and lazy, though you can reap the benefits of this with React as well), but it seems to me that the real problem is the fact that you're trying to render way to much. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
