[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-wasi-03-webassembly-zh":3,"article-related-wasi-03-webassembly-zh":32,"series-industry-05b76109-4a3b-415c-816f-b3b8e857939c":77},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":24,"views":28,"created_at":29,"published_at":30,"topic_cluster_id":31},"05b76109-4a3b-415c-816f-b3b8e857939c","wasi-03-webassembly-zh","WASI 0.3 正式版讓 WebAssembly 協作更順","\u003Cp data-speakable=\"summary\">WASI 0.3 把 WebAssembly 元件的非同步處理收斂到主機端，讓不同部件更容易一起運作。\u003C\u002Fp>\u003Cp>這份清單看完，你會知道 WASI 0.1、0.2、0.3 各自解決了什麼問題，也能判斷自己是該先補基礎、直接追元件模型，還是開始評估非同步整合。對已經在做 WebAssembly 服務的人來說，這 5 項足夠幫你決定要不要升級實作與調整架構。\u003C\u002Fp>\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>項目\u003C\u002Fth>\u003Cth>定位\u003C\u002Fth>\u003Cth>關鍵變化\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>WASI 0.1\u003C\u002Ftd>\u003Ctd>基礎抽象層\u003C\u002Ftd>\u003Ctd>把 OS API 抽離，讓 WebAssembly 能跑出瀏覽器\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>WASI 0.2\u003C\u002Ftd>\u003Ctd>元件模型導入\u003C\u002Ftd>\u003Ctd>加入 WIT，並整理 wasi-http、wasi-cli、wasi-clocks\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>WASI 0.3\u003C\u002Ftd>\u003Ctd>非同步整合\u003C\u002Ftd>\u003Ctd>改為由主機管理單一事件迴圈\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Wasmtime 46\u003C\u002Ftd>\u003Ctd>參考實作\u003C\u002Ftd>\u003Ctd>預計支援 WASI 0.3，且 async 預設啟用\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Component model 1.0\u003C\u002Ftd>\u003Ctd>下一階段目標\u003C\u002Ftd>\u003Ctd>持續補強 ABI 與跨執行環境相容性\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Ch2>1. WASI 0.1：先把 WebAssembly 從瀏覽器放出去\u003C\u002Fh2>\u003Cp>WASI 的第一步，不是炫技，而是把 WebAssembly 從單純的\u003Ca href=\"\u002Fnews\u002Fffmpeg-webcli-browser-video-editor-zh\">瀏覽器\u003C\u002Fa>技術，\u003Ca href=\"\u002Fnews\u002Fnewcore-turns-ai-agents-into-managed-identities-zh\">變成\u003C\u002Fa>能在更多環境執行的通用基礎。它的核心是把作業系統相關的 \u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa> 先抽象掉，讓同一份模組可以往伺服器、桌面或其他執行器延伸。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781682494700-rhtw.png\" alt=\"WASI 0.3 正式版讓 WebAssembly 協作更順\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>對開發者來說，這代表你不必一開始就被特定作業系統綁住。它先解決的是「能不能跑」這件事，之後才是「怎麼更好地跑」。\u003C\u002Fp>\u003Cul>\u003Cli>重點：OS API 抽象化\u003C\u002Fli>\u003Cli>用途：擴大到瀏覽器外執行\u003C\u002Fli>\u003Cli>意義：建立可攜式運算的第一層\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>2. WASI 0.2：元件模型把組裝方式先定下來\u003C\u002Fh2>\u003Cp>到了 WASI 0.2，重點就不只是執行，而是如何把不同語言、不同來源的 WebAssembly 部件拼成一個系統。這一版把元件模型帶進來，讓「模組之間怎麼對接」開始有共同語言。\u003C\u002Fp>\u003Cp>其中最關鍵的是 \u003Ccode>WIT\u003C\u002Fcode>，也就是 WebAssembly Interface Type。它像是元件之間的介面說明書，讓型別與功能描述能被一致理解；同時也整理出常見能力，例如 HTTP、命令列與時鐘。\u003C\u002Fp>\u003Cul>\u003Cli>\u003Ccode>WIT\u003C\u002Fcode>：定義介面的共同格式\u003C\u002Fli>\u003Cli>常見項目：\u003Ccode>wasi-http\u003C\u002Fcode>、\u003Ccode>wasi-cli\u003C\u002Fcode>、\u003Ccode>wasi-clocks\u003C\u002Fcode>\u003C\u002Fli>\u003Cli>價值：讓跨語言元件更容易互接\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>3. WASI 0.3：非同步處理改由主機統一管理\u003C\u002Fh2>\u003Cp>WASI 0.3 最重要的改變，是把原本各元件自己處理的事件迴圈收回到主機端。以前每個元件可能有自己的非同步邏輯，組起來時容易出現責任切割不清、整合成本偏高的問題。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781682493011-0ssj.png\" alt=\"WASI 0.3 正式版讓 WebAssembly 協作更順\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>新規格改成由主機管理單一事件迴圈後，元件之間的非同步互動就能放在同一套基礎上協調。這對需要同時處理 I\u002FO、請求轉發、背景工作或多個服務組合的場景特別有感。\u003C\u002Fp>\u003Cul>\u003Cli>變更前：各元件各自維護事件迴圈\u003C\u002Fli>\u003Cli>變更後：主機統一調度\u003C\u002Fli>\u003Cli>效果：降低非同步元件混用的摩擦\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>4. Wasmtime 46：實作跟上，才知道規格能不能用\u003C\u002Fh2>\u003Cp>規格成熟不代表立刻能落地，實作跟不跟得上才是關鍵。WASI 的參考實作 \u003Ca href=\"https:\u002F\u002Fwasmtime.dev\u002F\">Wasmtime\u003C\u002Fa> 預計在 46 版支援 WASI 0.3，並把 async 設為預設啟用，這讓開發者有機會直接觀察新規格在真實環境中的表現。\u003C\u002Fp>\u003Cp>如果你正在評估要不要導入新的 WebAssembly \u003Ca href=\"\u002Fnews\u002Fkimi-k26-open-source-coding-agents-zh\">工作流\u003C\u002Fa>，實作端的進度通常比文件更有參考價值。能先在 Wasmtime 上試出問題，後面移植到其他執行器時會省很多時間。\u003C\u002Fp>\u003Cul>\u003Cli>參考實作：Wasmtime\u003C\u002Fli>\u003Cli>版本焦點：46\u003C\u002Fli>\u003Cli>觀察重點：async 預設開啟後的相容性\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>5. Component model 1.0：現在做的是鋪路，不是收尾\u003C\u002Fh2>\u003Cp>Bytecode Alliance 對 WASI 的定位很清楚：這不是終點，而是往 Component model 1.0 前進的中繼站。接下來還有 ABI 改善、更多執行環境實作，以及讓規格更容易被採用的工程化工作。\u003C\u002Fp>\u003Cp>換句話說，WASI 0.3 的價值不只在於「能不能更順」，而是先把元件協作的共通規則定穩。當非同步、介面定義與主機責任都對齊之後，後續才有機會真正跨平台、跨語言地擴大使用。\u003C\u002Fp>\u003Cul>\u003Cli>方向：邁向 Component model 1.0\u003C\u002Fli>\u003Cli>待解問題：ABI 與實作一致性\u003C\u002Fli>\u003Cli>長期目標：更廣泛的相容環境\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>哪種適合你\u003C\u002Fh2>\u003Cp>如果你現在還在理解 WebAssembly 能做到什麼，先看 WASI 0.1 就夠了；如果你已經在設計元件化系統，WASI 0.2 的 WIT 和介面定義會更重要；如果你最在意的是多個非同步部件怎麼一起跑，WASI 0.3 才是這次真正該跟進的版本。\u003C\u002Fp>\u003Cp>而若你是想評估實際導入時機，先追 Wasmtime 的支援進度最務實。它能幫你判斷現在是適合觀望、試作原型，還是可以開始調整既有架構。\u003C\u002Fp>","WASI 0.3 正式版把非同步處理收斂到主機端單一事件迴圈，適合先看 5 個重點再決定要不要跟進升級。","www.publickey1.jp","https:\u002F\u002Fwww.publickey1.jp\u002Fblog\u002F26\u002Fwasi_03webassembly_component.html",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781682494700-rhtw.png","industry","zh","f2a8a044-c05b-4ff9-9abd-1314ffc20f79",[17,18,19,20,21,22,23],"WASI","WebAssembly","元件模型","非同步處理","Wasmtime","WIT","Bytecode Alliance",[25,26,27],"WASI 0.3 的核心變化，是把非同步處理交給主機統一管理。","WASI 0.2 先把元件模型與 WIT 定下來，讓跨語言組裝有共同規則。","若要看實際落地，Wasmtime 的支援進度比規格文字更值得追蹤。",0,"2026-06-17T07:47:43.774454+00:00","2026-06-17T07:47:43.765+00:00","caa87b65-9bbc-46fe-bba8-4f4158dd2d8b",{"tags":33,"relatedLang":36,"relatedPosts":40},[34],{"name":18,"slug":35},"webassembly",{"id":15,"slug":37,"title":38,"language":39},"wasi-03-official-webassembly-component-async-en","WASI 0.3正式版でWebAssembly連携が楽になる","en",[41,47,53,59,65,71],{"id":42,"slug":43,"title":44,"cover_image":45,"image_url":45,"created_at":46,"category":13},"2a151488-09f9-4aa8-a654-3f1d9d7e159c","china-ai-open-source-efficiency-global-sales-zh","中國 AI 轉向：開源、效率、出海","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781702271555-i3q3.png","2026-06-17T13:17:25.59471+00:00",{"id":48,"slug":49,"title":50,"cover_image":51,"image_url":51,"created_at":52,"category":13},"4a2fbd38-b5c2-4590-9d4b-87f39f95ab9c","ergo-hestia-pricing-time-to-market-databricks-zh","ERGO Hestia 4 招縮短定價上線","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781697768906-9krk.png","2026-06-17T12:02:22.440161+00:00",{"id":54,"slug":55,"title":56,"cover_image":57,"image_url":57,"created_at":58,"category":13},"0cf56d85-887b-4fb1-8589-046da6513d26","openai-oracle-universal-credits-enterprise-buying-zh","OpenAI 進 Oracle 企業採購圈","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781696892976-sx90.png","2026-06-17T11:47:35.092555+00:00",{"id":60,"slug":61,"title":62,"cover_image":63,"image_url":63,"created_at":64,"category":13},"dd3d240a-0f53-49a4-90a5-cac17171f3fd","managed-chatgpt-access-policy-layers-zh","4 層規範決定企業版 ChatGPT 可怎麼用","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781695973066-pbtw.png","2026-06-17T11:32:17.633521+00:00",{"id":66,"slug":67,"title":68,"cover_image":69,"image_url":69,"created_at":70,"category":13},"c826a181-b373-4a9e-a494-1f8f4bc86c3c","openai-service-terms-app-risk-users-zh","OpenAI 服務條款把第三方 App 風險留給使用者","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781695063951-v71m.png","2026-06-17T11:17:21.223004+00:00",{"id":72,"slug":73,"title":74,"cover_image":75,"image_url":75,"created_at":76,"category":13},"7b6bec1f-4f42-4b60-a72d-027bf95a36e7","anthropic-fable-shutdown-own-your-models-zh","Fable 停用逼你把模型收回來","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1781687002361-q7fl.png","2026-06-17T09:02:52.16704+00:00",[78,83,88,93,98,103,108,113,118,123],{"id":79,"slug":80,"title":81,"created_at":82},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":84,"slug":85,"title":86,"created_at":87},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":89,"slug":90,"title":91,"created_at":92},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":94,"slug":95,"title":96,"created_at":97},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":99,"slug":100,"title":101,"created_at":102},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":104,"slug":105,"title":106,"created_at":107},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":109,"slug":110,"title":111,"created_at":112},"0740e53f-605d-4d57-8601-c10beb126f3c","google-pushes-gemini-transition-to-march-2026-zh","Google 把 Gemini 轉換延到 2026 年 3…","2026-03-26T07:30:12.825269+00:00",{"id":114,"slug":115,"title":116,"created_at":117},"e660d801-2421-4529-8fa9-86b82b066990","metas-llama-4-benchmark-scandal-gets-worse-zh","Meta Llama 4 分數風波又擴大","2026-03-26T07:34:21.156421+00:00",{"id":119,"slug":120,"title":121,"created_at":122},"183f9e7c-e143-40bb-a6d5-67ba84a3a8bc","accenture-mistral-ai-sovereign-enterprise-deal-zh","Accenture 攜手 Mistral AI 賣主權 AI","2026-03-26T07:38:14.818906+00:00",{"id":124,"slug":125,"title":126,"created_at":127},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]