Our great sponsors
-
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.
-
nontrapping-float-to-int-conversions
Discontinued Proposal to add non-trapping float-to-int conversions to WebAssembly
-
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.
It is true that wasmtime (or more clearly, Mozilla) had people that were active in the Wasm Working Groups. They aren't alone though! Google, Intel, Parity, Fastly, Cloudflare and others are super active too. Keep in mind that at Wasmer we are a small team of ~4-6 developers. We do our best but we can't be as present and active as larger teams, for obvious reasons. We do contribute actively to the Wasm C API, Wasm C++ API, WIT, WASI etc. working groups for example. We also provide WAPM, a Wasm Package Manager, and we provide language integrations of WebAssembly inside Python, Go, PHP, Ruby, Java, Postgres, and others (by contributors) like R, Elixir, Dā¦ (see the complete list actual). It helps to spread WebAssembly everywhere and to create usecases. That's really interesting.
JavaScript BigInt to Wasm i64 integration,
Bulk memory operations,
Multi-value,
Import/Export of Mutable Globals,
Non-trapping float-to-int conversions,
I reckon it's a wrong statement. Reading https://github.com/WebAssembly/proposals, we see that the following proposals are finished and part of the the latest draft of the spec:
Reference Types,
Sign-extension operators,
Now, strictly technically speaking, wasmtime comes with a single compiler: Cranelift. It is an awesome piece of software. Cranelift was a standalone project until recently, where it has been merged into wasmtime directly, which is a move I find regrettable, but that's the situation. On the other hand, Wasmer comes with 3 compilers, namely Singlepass, Cranelift and LLVM (see the Pluggable Infrastructure Section of the article, or an older article A WebAssembly Compiler tale). Each of them address particular needs. That's important to understand that Wasm has a compilation step (from Wasm bytes to executable code), and an execution step (executing the compiled code). It is false for interpreters, but Wasmer isn't an interpreter. So, back to our 3 compilers: