Will WebAssembly make the Audio API and WebGL obsolete?

I recently learned about Webassembly, and I'm surprised because it means that I can write really, and import really highlights the heavy parts of my application in C or C ++.

Now my question is, how does WebAssembly affect Audio Api and WebGL? I mean that the Audio API is high-level and depends on javascript, since all manipulations with audio, midi, etc. Work in webassembly? Do we work directly with the above APIs or use some other third-party library, such as http://www.portaudio.com/ ? Same with WebGL, are we using the WebGL or C ++ OpenGL interface right now when we have low level access?

I'm sorry if that sounds naive, but I'm honestly embarrassed. I am really motivated, so please help me understand.

+4
source share
1 answer

Your question is very close to this in the web API with one difference: how did the web API influence?

Web APIs are not affected at all; WebAssembly needs to call JavaScript. There are libraries that make this easier, like SDL2 . Same thing with GL . You can also create your own wrappers instead of using pre-made ones.

WebAssembly API JavaScript, : . , .

+3

Source: https://habr.com/ru/post/1675019/


All Articles