Closed lokiiarora closed 1 year ago
Hi, did you see #18 ?
Oh no ! I did not see this, so the baseline being currently, it is not possible right?
I think it's currently impossible to workaround that, and I'm not sure it's worth the effort if it could, since SharedArrayBuffer
is present in most major browser engines. It probably also affects performance in a negative way.
Makes sense, thanks !
Is it possible to have a custom build of wasm-vips without
SharedArrayBuffer
and Workers / concurrency ? We wrap wasm-vips to build an internal texture compressor, it becomes slightly harder to package this as a library with the Worker Pattern.