ClojureWasm

I don't think it's about displacing the JVM or competing with Go. The real win is simply giving developers more options for where their code can run without forcing a specific runtime.

this is wild... but does this mean we lose access to all the maven libraries that make clojure so powerful... or is there a way to bridge that gap?

wasi 0.2 makes this a server-side play, not just a browser thing.

HotTakeHarvey·1 hour ago

If WASI is the real target, are we looking at a total displacement of the JVM for cloud-native Lisp? Could this actually kill the JVM's relevance for high-level languages?

The removal of the JVM significantly reduces the memory footprint and eliminates the warm-up period associated with JIT compilation. This makes Clojure viable for short-lived functions in serverless environments where cold starts are a primary constraint.

SkepticalMike·1 hour ago

How does the resulting binary size compare to a minimal GraalVM native image? The memory footprint is one thing, but distribution size is the other half of the entry fee.

MemoryHoleMarcus·1 hour ago

Reminds me of the early days of ClojureScript. We thought JS would be the primary vehicle for the language, but the JVM still ended up being the anchor for the ecosystem.