9 ms·
This looks neat but pure port seems to be stretching it: >ffmpeg.wasm is a pure Webassembly / Javascript port of FFmpeg >@ffmpeg/core contains WebAssembly cod
by bragr 4y ago
This looks neat but pure port seems to be stretching it:
>ffmpeg.wasm is a pure Webassembly / Javascript port of FFmpeg
>@ffmpeg/core contains WebAssembly code which is transpiled from original FFmpeg C code with minor modifications [1]
[1] https://github.com/ffmpegwasm/ffmpeg.wasm#what-is-the-license-of-ffmpegwasm https://github.com/ffmpegwasm/ffmpeg.wasm#what-is-the-licens...
- graderjs 4y agoNot a stretch at all as that’s the general meaning of port in wasm… it’s supposed to be a transpilation target for other langs.
- miloignis 4y agoI'm not sure I understand your criticism - in what way is it not a port to pure webassembly? I'm tempted to hazard a guess that you expected a rewrite, but that's not what port normally means - if I said I ported ffmpeg to RISC-V no one would have expected me to have rewritten all of ffmpeg in RISC-V assembly, they would expect that I did mild-to-medium modifications on the source and build system to get it compiling to RISC-V machine code (which is analogous to the ffmpeg.wasm project). If that's not what you meant, I apologize for interpreting incorrectly!