Go-wasm-bake Alternatives

Similar projects and alternatives to go-wasm-bake

go

2,067 119,564 10.0 Go go-wasm-bake VS go

The Go programming language
wasmtime

172 14,407 10.0 Rust go-wasm-bake VS wasmtime

A fast and secure runtime for WebAssembly
InfluxDB

www.influxdata.com sponsored

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.
TablaM

151 183 0.0 Rust go-wasm-bake VS TablaM

The practical relational programing language for data-oriented applications
wasmer

131 17,786 9.9 Rust go-wasm-bake VS wasmer

🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
rr

102 8,621 9.6 C++ go-wasm-bake VS rr

Record and Replay Framework
quickjs-emscripten

21 1,122 9.4 TypeScript go-wasm-bake VS quickjs-emscripten

Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
wizer

10 875 7.0 Rust go-wasm-bake VS wizer

The WebAssembly Pre-Initializer
WorkOS

workos.com sponsored

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.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better go-wasm-bake alternative or higher similarity.

Suggest an alternative to go-wasm-bake

go-wasm-bake reviews and mentions

Posts with mentions or reviews of go-wasm-bake. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-02.

Bytecode Alliance
8 projects | news.ycombinator.com | 2 Jun 2021

> So how does this work? Before the code is deployed, as part of a build step, we run the JS code using the JS engine to the end of initialization.
I also did basically this exact same thing for Go [0] when I realized their initialization in WASM was very heavy[1]. Basically I ran up until the real Go main started which includes a ton of runtime package/data initialization, and took a snapshot of the data and baked it back into the WASM and removed all the pre-main code. Granted this was years ago so I don't know if it still works on generated code today, but the idea is the same.
I think languages compiling to WASM, if they can, should run their initialization code and snapshot the data. A lot of people don't realize the number of init instructions to bootstrap a runtime these days. Go alone has thousands of instructions just to initialize the unicode tables.
0 - https://github.com/cretz/go-wasm-bake