Post

Go needs a Wasm implementation that supports having the language runtime in a separate module from the app -- essentially dynamic linking. Needed so apps can share the same runtime rather than every app bundling its own copy. But Go haaaaaaaates dynamic linking.

Without that, Go apps just can't achieve anywhere near the efficiency of JavaScript in the Workers runtime model. Alternatively, you can run Go in containers (released yesterday) but they will be less distributed and more expensive than Workers.

Totally valid reasons around this! I figured that runtime stuff for JS is what makes workers so nicely priced. Hmmmmm. weekend project: reengineer all of go from the ground up to support this (kidding, mostly…)

0 reposts0 likes

No replies yet.