All geek questions in one place

The future of your own client after WebAssembly Post-MVP

I am sure that after WebAssembly Post-MVP, asm.js will be deprecated. Already, several existing asm.js projects are already starting to use WebAssembly. The JS engine (V8) is also starting to use asm.js for WebAssembly, so even if older projects never migrate, end users will still get partial benefits from WebAssembly.

My question is: what about a native customer? It is not implemented in the JS engine, so this can be a problem. The native client seems to be out of date. In the foreseeable future, will the personal client be completely removed from Chrome? I would like to see some reduction in the binary size of Chrome.

Side questions:

  • After thread / gc / simd / exception is included in WebAssembly, is there anything else that the native client has but is missing from WebAssembly (migration blocking)?
  • It took WebAssembly about 2 years to achieve MVP, what is the expected time to complete any of Post-MVP?
  • It seems that the WebAssembly group solves several Post-MVP functions at once, and not one by one, will this make the completion of one of them slower?
+4
source share
1 answer

We answer only side questions, because I no longer work on my own client. Google plans are their own to talk about, so I will do this wiki.

2017/05/20 NaCl glibc. libc, , . NaCl GCC. - musl libc, LLVM- NaCl PNaCl.

2017/05/30 Chromium PNaCl WebAssembly.

, :

  • , , . , 64- , Double-Sandbox . WebAssembly .
  • JavaScript postMessageAndAwaitResponse. .
  • API- Pepper. API- -.
  • mprotect ( ).
  • POSIX .
  • goto .
  • " ".
  • , seq_cst .
  • , NaCl.

Native Client. .

WebAssembly MVP. , . , , . , .

+3

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

More articles:


All Articles