For responsive JS, the main compute algorithm should not be on the main thread. So, the UI is the app and it talks to a "remote" engine.
From the UI/App perspective the "remote" compute could be on a worker thread or it could be on a server (say, Jupyter). So, architect the code to deal with both cases in similar ways.
For responsive JS, the main compute algorithm should not be on the main thread. So, the UI is the app and it talks to a "remote" engine.
From the UI/App perspective the "remote" compute could be on a worker thread or it could be on a server (say, Jupyter). So, architect the code to deal with both cases in similar ways.