[Feature Request] WASM and WASI

[kyrvlasiuk]

Request

Add wasm and wasi compile targets

Motivation

Same reason why everyone is doing it. I am on mobile, I might elaborate further, if no one else has. Or you can nuke this one.

Description and Requirements

TBD

[Mogball]

Closing this because it's not in our immediate roadmap and isn't very useful to keep in our issue tracker.

[huntc]

Using Python sans WASI in the context of the web browser is compelling to me. The current strategy of running a Python interpreter under WASM is underwhelming. Therefore, having a Python-like-native-wasm offering may be interesting in general terms. It could help drive Mojo adoption perhaps. Just sharing some hopefully useful thoughts.

(For comparison, consider TypeScript vs AssemblyScript.)

[matthew-dean]

@huntc I agree that having WASM as a target would explode interest in Mojo who currently only have Rust available (in practical terms) to speed up performance over JS.

Case and point, I actually found this issue because I was going to start researching what would be involved in migrating a major open source (JS) project to Mojo, so I started with Googling Mojo + WASM and ended up here, which is currently a dead-end. I know Mojo development is early days, but I just wanted to give my +1 that as an open source dev, I'm eager to explore building Mojo-based JS tooling instead of Rust- or Go-based tooling.

[johnoscott]

WASM is already a heterogenous target given that it can target WebGPU and both of them can sit on top of exotic hardware. That very much sounds like a job for Mojo ! +1 for adding this.