On: Firefox’s new streaming and tiering compiler

[gigatexal]

Yeah I read the article too and thought: but what can I do with wasm?

[kbumsik → gigatexal]

You can import C (and many others) libraries without re-implementing it in JS for browsers. In my company's case, we compile C-written libopus almost directly to encode audio streams into Opus on browsers, not on servers. In this way we benefit much less data traffic and server CPU loads.

[QAkICoU7IDNkpFu → kbumsik]

>You can import C (and many others) libraries

This means compiling the lib to wasm, right? At first I was thinking of running JS clientside that imports some C lib somehow, which confused me.

[kbumsik → QAkICoU7IDNkpFu]

Yes. The C lib will be compiled into wasm. You can use the wasm-compiled code in a browser through JS wrappers. So you can say importing C lib on JS client side anyway.

Note that wasm's main objective is to run non-JS code on browsers, not for a faster JS.

Here is the best overview and tutorial I've ever seen in HN , if you are interested: https://news.ycombinator.com/item?id=15958827

[gigatexal → kbumsik]

So you could do the same with Cython then, too? Interesting.

[kbumsik → gigatexal]

I've never experienced with Cython. But if Cython is to compile anPython file into a C file then probably.