{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Rust's WASI Targets: What's Changing?","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/3bd612da\"></iframe>","width":"100%","height":180,"duration":433,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/rusts-wasi-targets-whats-changing.\n             In this post we'll discuss the introduction of the new targets, the motivation behind it, and what that means for existing WASI targets. \n            Check more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #rust, #rustlang, #wasm, #wasm32, #wasip2, #wasi-targets, #rust-changes, #rust-update,  and more.\n            \n            \n            This story was written by: @Rust. Learn more about this writer by checking @Rust's about page,\n            and for more stories, please visit hackernoon.com.\n            \n                \n                \n                Rust 1.78 will introduce new `wasm32-wasip1` (tier 2) and `wasms32- wasip2' (tier 3) targets. Users of WASI 0.1 are encouraged to begin migrating to the new** 'wasm 32-wasi' target. The existing `wask32-unknown-unknown' and 'wassam32-emscripten' targets are unaffected by this post.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}