@krzyzanowskim@Migueldeicaza I updated my local copy of the swift project and noticed the addition of wasmkit as well. The JSC numbers were quite compelling with the ongoing JIT, but very excited to see the wasmkit hosting option come to Swift in a nice cross-platform way.
@heckj@krzyzanowskim@Migueldeicaza right — apple/swift already depends on wasmkit, though afaict it’s currently only used for testing the wasi target. This undertaking will quite possibly require bringing it into the toolchain though, at least on Windows/Linux where we can’t use JSC. I do hope the swift team agrees with this approach because it’ll be an amazing way to dogfood WasmKit (and Swift Wasm).
@Migueldeicaza I understand and agree with the dependency concerns, but I think it's just making a lot more work to make an ad hoc abi. That's 100% throwaway work for everyone.
@Migueldeicaza I haven’t gotten my head around what it does for swift and why I care (I don’t mean that in a troll way - I mean that in an “I don’t get it yet” way)
@dimsumthinking swift build system can use plugins, some plugins are too large and slow down every build because you first have to build those plugins
Now you can use pre compiled binaries that work everywhere
That said, the even better part is that swift on wasm is solid enough for this and creates a reason to make it even better, not just a “cute thing it can do”.
Add comment