Update _posts/2026-01-22-ten-years-of-webassembly-a-retrospective.md

Co-authored-by: Luke Wagner <mail@lukewagner.name>

Author: 2 people

_posts/2026-01-22-ten-years-of-webassembly-a-retrospective.md

@@ -72,7 +72,7 @@ The formal announcement was coordinated: on June 17, 2015, all four browsers sim
 
 As the project progressed, Lin Clark's communication was instrumental in building community understanding, such as in Mozilla blogs like [Creating and working with WebAssembly modules](https://hacks.mozilla.org/2017/02/creating-and-working-with-webassembly-modules/).
 
-For the group working on Wasm, the pressure to ship was intense. "Ship as fast as you humanly can before this whole coalition falls apart," was the prevailing sentiment, according to Wagner. In retrospect, the urgency proved prescient. Had WebAssembly been delayed, the [Spectre vulnerability](https://spectreattack.com/)—disclosed in early 2018—might have complicated the threading story and handed ammunition to those who preferred PNaCl's out-of-process isolation model. Firefox shipped first in March 2017, with Chrome following weeks later. By the end of the year, all four major browsers supported WebAssembly.
+For the group working on Wasm, the pressure to ship was intense. "Ship as fast as you humanly can before this whole coalition falls apart," was the prevailing sentiment, according to Wagner. In retrospect, the urgency proved prescient. Had WebAssembly been delayed, the [Spectre vulnerability](https://spectreattack.com/)—disclosed in early 2018—might have [complicated](https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack) the [threading story](https://developer.chrome.com/blog/meltdown-spectre#high-resolution_timers) and handed ammunition to those who preferred PNaCl's out-of-process isolation model. Firefox shipped first in March 2017, with Chrome following weeks later. By the end of the year, all four major browsers supported WebAssembly.
 
 ## Treating it as a real thing