WebAssembly becomes a W3C Recommendation

Re:WebAssembly becomes a W3C Recommendation by s_y_n_t_a_x on Monday December 16, 2019 @01:02PM (#21805280)

Figma uses it for their design editor.

PSPDFKit uses it for their pdf editor.

Unreal Engine/Unity uses it for their browser support.

It's used in production in many places either as modules or entire apps.

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by steveklabnik on Monday December 16, 2019 @01:06PM (#21805327)

1password recently moved their browser plugin too https://blog.1password.com/1password-x-may-2019-update/

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by alaaf on Monday December 16, 2019 @01:41PM (#21805734)

Figma uses Emscripten which is technically not Webassembly (to my knowledge)

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by echeese on Monday December 16, 2019 @01:45PM (#21805771)

Emscripten has been able to compile to WASM since before WASM was implemented in browsers. It became the default output earlier this year.

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by azakai on Monday December 16, 2019 @06:48PM (#21808882)

Some more detail: Emscripten has defaulted to emit wasm even earlier, in May 2018. The change this year was to switch how that wasm is emitted, from the old fastcomp+asm2wasm path to the new LLVM wasm backend.

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by echeese on Wednesday December 18, 2019 @09:33AM (#21825191)

I was actually thinking about the switch from asm.js to WASM (v1.38.1) but apparently that was last year. Whoops!

[ Parent | on HN ]

Re:WebAssembly becomes a W3C Recommendation by timClicks on Monday December 16, 2019 @01:46PM (#21805777)

Emscripten has a WASM backend, it was originally JavaScript only.

[ Parent | on HN ]