The talk has predicts a lot of what is happening around wasm.
The irony is that with its 3% market share, if it was today on the age of Chrome OS based Web, Google would have been able to push it no matter what.
To make a tl;dr, the video talks about a technology called asm.js which other applications end up compiled into so they can run with near-native speeds on any system which supports asm.js. This technology ends up being a compilation target meaning that JS gets eventually forgotten as a language because everyone just compiles everything into asm.js which is executed natively on the kernel.
Just do a s/asm.js/WASM/g and it'll suddenly start making sense.
What we're yet to see is this last point becoming the default, so execution of user programs kind-of makes a circle by returning to kernel mode, except now a trusted WASM-to-native compiler/runtime is responsible for ensuring system safety. Might happen in the next few years.
[1]: https://en.wikipedia.org/wiki/Singularity_%28operating_syste...
The idea is still really interesting, though. It's almost like micro-containerization. I was reading this and it's what sold me on attempting it:
https://www.techtarget.com/searchitoperations/news/252527414...