-
Would it be feasible to make Dodrio run in a web worker by doing the diffing and everything else in the worker and only applying the change list in the main thread? perhaps the bridging can use a Shar…
-
Generation of the image can sometimes be incredibly slow because of the size of the function created.
We pause at each pixel to stop browser tab lag/freezing but this also is adding onto the already …
-
**Is your feature request related to a problem? Please describe.**
Our internal app often generates large graphs, it would be nice to run the render in a web work to not lock up the page.
**Descri…
-
### Feature Description
When dealing with huge entities with lots of one to many and many to many joins, the typeorm hydration process takes a painful amount of time. This has been highlighted in …
-
native works bc of thread:::spawn. This needs to be genericised to also work for web workers. Investigate how to do this. To start, here's a chatGPT answer that might get you started on the right path…
-
**Description**
[Web Workers API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers) instead of sources of a file gets source of the `index.html`.
I mean `fetch()`…
-
It seems taking very long time rendering large document especially those including MathJax rendered formulas. Since loading an image is asynchronously done by browser, this library seems to be the onl…
-
### Describe the issue
I'm running into issues trying to use the WebGPU or WASM backends inside of a ServiceWorker (on a chrome extension). More specifically, I'm attempting to use Phi-3 with trans…
-
### Describe the bug
I'm using an inlined (?worker&inline) web worker that dynamically imports some other libraries.
It works well in dev mode but fails in the production build since the filenames …
-
Wonder if the GUI would have less responsive issues if Web worker was used ?
Also if WASM was used ?