Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
As a Rust beginner and Vue user, I wonder how to render the WebAssembly on the browser directly. So I did some investigation on how jsbin and webassembly.studio work. It took some time to finally realize that the generated page is embedded on the IFrame element. So I started to trace Rust Playground and mdBook source code and write on own POST method on wasm-pack.
As a Rust beginner and Vue user, I wonder how to render the WebAssembly on the browser directly. So I did some investigation on how jsbin and webassembly.studio work. It took some time to finally realize that the generated page is embedded on the IFrame element. So I started to trace Rust Playground and mdBook source code and write on own POST method on wasm-pack.
As a Rust beginner and Vue user, I wonder how to render the WebAssembly on the browser directly. So I did some investigation on how jsbin and webassembly.studio work. It took some time to finally realize that the generated page is embedded on the IFrame element. So I started to trace Rust Playground and mdBook source code and write on own POST method on wasm-pack.
As a Rust beginner and Vue user, I wonder how to render the WebAssembly on the browser directly. So I did some investigation on how jsbin and webassembly.studio work. It took some time to finally realize that the generated page is embedded on the IFrame element. So I started to trace Rust Playground and mdBook source code and write on own POST method on wasm-pack.
I think it'd be better to use trunk instead of wasm-pack for this. Great work though, looking forward to being able render WASM on the playground.