It depends on what kind of an app you are building. If you create an app streaming real time data via a socket connection and you also have expensive JS logic to parse the data, you want to use the vdom worker.

In case you create something simple, you can deactivate it for boosting the performance.

We can further enhance this concept: We could add a method inside the main thread to dynamically create a vdom worker, so that you can switch between using the worker or not at run time. You would still need to know at which point to active or remove the worker.

For super expensive apps, we could also create multiple vdom workers and split the update calls between them. I have not encountered a case where the vdom worker is this busy yet though.

Best regards,

Tobias