Worth noting, this page says that Firefox doesn’t support it yet but it’s enabled in the current version. Safari is the only major browser yet to ship it.
It’s a slow road, but this, and some string handling issues, were low hanging fruit in browser wasm. I still think we’re getting close to the phase transition from “browsers run wasm in their javascript engines” to “browsers compile javascript to wasm”. Once we hit that inflection point, javascript as a programming language can die.
I am not a fan of JS at all and I would love to have been born into a parallel universe where wasm came before JS and we had a wild, flourishing front-end language ecosystem, but in this universe, it’s very unlikely for JavaScript to die within the coming decades even if it entered a death trajectory today. There’s simply too much stuff built on it and too many people that swear by it.
Worth noting, this page says that Firefox doesn’t support it yet but it’s enabled in the current version. Safari is the only major browser yet to ship it.
It’s a slow road, but this, and some string handling issues, were low hanging fruit in browser wasm. I still think we’re getting close to the phase transition from “browsers run wasm in their javascript engines” to “browsers compile javascript to wasm”. Once we hit that inflection point, javascript as a programming language can die.
I am not a fan of JS at all and I would love to have been born into a parallel universe where wasm came before JS and we had a wild, flourishing front-end language ecosystem, but in this universe, it’s very unlikely for JavaScript to die within the coming decades even if it entered a death trajectory today. There’s simply too much stuff built on it and too many people that swear by it.