Re:V8 release v6.8
by davidgrenier on Thursday June 21, 2018 @08:04AM
(#17364314)
Most of said languages are already adopted. You can expect languages running server-side to target WebAssembly first.
The other great thing is that WASM libraries written in all sorts of languages will be available to all of them.
There are still problems with WASM in the areas of multithreading, shared data structures, and memory barriers (think advanced/concurrent GC implementations). Because of this, languages do not automatically, cleanly and efficiently map to WASM yet.
Most of the pre-existing server side come with their own baggage. PHP powers most of the internet, just saying :)
Re:V8 release v6.8
by davidgrenier on Thursday June 21, 2018 @09:12AM
(#17364735)
I don't have a problem using good WASM libraries that were written in PHP. To target WASM, a PHP compiler would have to respect the WASM semantics which is what I will consume.
Re:V8 release v6.8
by RussianCow on Thursday June 21, 2018 @01:59PM
(#17367658)
For a dynamic language to run on WASM, you would have to bundle its runtime with your application, which is probably a deal-breaker for many use cases.
What might happen instead is that there will be a sudden burst of front end languages running on WASM, which will allow some front end people to completely avoid Javascript.
It's hard to predict what the adoption of those languages will look like, there's a million factors in play and few of them are technical.