https://www.reddit.com/r/elixir/comments/1dca6sl/comment/l7yw6sd/?utm_source=thinkingelixir&utm_medium=shownotes

This was linked/mentioned on a recent Thinking Elixir Podcast

Hey, the creator of Hologram here. Hologram is not using Firefly under the hood - it transpiles BEAM definitions directly to JavaScript, and it has a different scope than FireFly in general, think ElixirScript + LiveView + Surface. Btw expect playable version soon!

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.

I think the potential is unlimited, you basically have the full-blown elixir/erlang capabilities at your disposal. You can write the part that is responsible for interaction with dom (from what I remember webassembly standard doesn’t include this) and write entire frontend applications in elixir, not having to go back to JS ever again.

Liveview is great, the biggest selling point is that you don’t have to write JS, however it has limitations for more involved applications, and currently people end up using a frameworks like react to solve this limitation, which is not something I enjoy doing.

For more possible features, think of applications as the native ones we use, the only difference is that it lives in browser.

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.