Skip to content

Commit a54fd0a

Browse files
ericgregoryricochet
authored andcommitted
correct spelling on Fil's name
1 parent 2c82715 commit a54fd0a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ This writer has certainly used the "neither web nor assembly" line more than onc
6262

6363
With the Chrome and Firefox teams on the same page, the co-designers turned to the teams at Apple and Microsoft.
6464

65-
Microsoft's Chakra team, which powered the Edge browser's JavaScript engine, had already implemented Asm.js optimizations—Wagner had personally relicensed Mozilla source code to make adoption easier. After some "intense Q&A" (in Wagner's words), the Chakra team got on board. At Apple, JavaScriptCore team lead Phil Pizlo was instrumental in securing buy-in.
65+
Microsoft's Chakra team, which powered the Edge browser's JavaScript engine, had already implemented Asm.js optimizations—Wagner had personally relicensed Mozilla source code to make adoption easier. After some "intense Q&A" (in Wagner's words), the Chakra team got on board. At Apple, JavaScriptCore team lead Fil Pizlo was instrumental in securing buy-in.
6666

6767
The four browser engines—Mozilla's SpiderMonkey, Google's V8, Microsoft's Chakra, and Apple's JavaScriptCore—would ship WebAssembly support within months of each other. Bastien, who chaired the WebAssembly Community Group during this period, helped set up the organizational structure and operating pace for the W3C standardization process. Before Wagner's first public commit, the team hashed out the basic shape of the project in a shared Google Doc. Wagner then transcribed those agreements into public markdown files.
6868

0 commit comments

Comments
 (0)