Re: [heycam/webidl] Exposing an interface "on all globals" (#468)

> I think worklets are intentionally small in their API surface and therefore I think the preference is that nothing additional is exposed there, unless it adds sufficient utility. It's not entirely clear they need URL parsing (e.g., they don't want fetch()) or text encoding/decoding.

It is the current thinking of the Audio Working Group that indeed, we want the set of APIs available inside an `AudioWorkletGlobalScope` to be as minimal as possible. In particular, exposing APIs that can block execution for long periods of time or are asynchronous are not to be exposed.

In addition, my opinion is that it would be best to not expose API that would encourage mis-use of the `AudioWorklet` API. For example, string manipulation for internationalization or anything but _executing_ WASM code is best done outside the worklet and transferred.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/468#issuecomment-368061721