Preliminary results for upgrade from Wasmer 0.3.x to 1.x

🧵
First off, NO MORE C HEADERS! The previous version of the Go bindings required defining a C header that described all of the host functions. VSCode doesn't check these things, nor do code hints help with it at all. Massive pain.
Next up, CI tests have been sped up between 4-10x -> I believe this is largely due to Wasmer's new architecture for compiling modules to native code before execution. Swift modules could previously take up to a few seconds to cold-start (both in CI and in real-life).
ARM support: Suborbital's core now runs on AMD64 and ARM64 architectures, on Linux or Mac! This was completely free, I didn't need to do anything. All I need to do now is create multi-arch Docker containers (I've ordered a Raspberry Pi for easier testing)
Benchmarks: Rust Runnables benchmark around the same as before, but Swift Runnables gain an order of magnitude of performance with Wasm 1.x (Swift modules are around 10x larger than Rust modules). Also, Rust performance was already amazing 🙂
Hopefully next: multiple return values. I can finally stop using in/out pointers 🙏🏼

I hope to test this out today, along with some continued updates and refactors.
You can follow @cohix.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.