Last I heard Firefly was on hold for the WASM spec to mature. I’m sure someone closer to the project can provide more detail, but it ain’t cheap to pay for the kind of expertise Firefly needs, and if the spec still needs to make progress the opportunity cost might not make sense at the moment.
MrDoops
SichangHe
dimitarvp
LostKobrakai
SichangHe
The author explained the situation in a latest issue. To summarize, the problem of WASM support is hard, and the author does not have time.
4
spritefullake
this is sad, I wanted to be able to run an elixir library I wrote in a local-first environment. Think easy distribution of the web + the security of not sending your data to a server in order to execute a code. I guess I’m limited to native distribution or switching to a different language that can compile to WASM easily…
0
venkatd
I do feel like something more like Hologram (transpile to javascript) may suffice. There’s already precedent there with other languages like clojurescript, elm, gleam. And ElixirScript got pretty far in that journey.
The main downside is the OTP primitives would not work as expected.
1
bartblast
Creator of Hologram
Just wanted to clarify that OTP primitives are on the roadmap for Hologram, so you’ll get client-server compatibility - and potentially being able to treat the client as another node in the cluster.
It will probably be without preemptive scheduling, but unless you’re running hundreds of processes on the client-side - which I don’t see a practical use case for - this shouldn’t be a problem at all.
2
i-n-g-m-a-r
cmo
Stack switching and threads are the next major items of focus for WASM, so maybe Firefly will become viable in the not too distant future.
0