It's worth noting that WASM will (eventually) enable other languages to run in the 'browser VM' and this loss of JS' monopoly (whether as a source language or a

It's worth noting that WASM will (eventually) enable other languages to run in the 'browser VM' and this loss of JS' monopoly (whether as a source language or a compilation target) will cause some of the pace of innovation to shift away from JS and onto WASM. Right now, the ecosystem has a lot of churn for exactly three reasons: - browser vendors keep adding 'web platform' APIs that are only callable through JS - new spins on paradigms are popping up on how to structure single-page applications - the JS language itself is getting new features after being stagnant for years When any one of these quiets down, the churn will slow.