# Phoenix LiveView with WebAssembly

**URL:** <https://forum.elixirforum.com/t/phoenix-liveview-with-webassembly/52607>\
**Category:** Discussions\
**Tags:** phoenix, javascript, wasm, liveview, webassembly\
**Created:** [December 18, 2022, 10:53am UTC](https://forum.elixirforum.com/t/phoenix-liveview-with-webassembly/52607 "2022-12-18T10:53:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![derpycoder](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/derpycoder/32/31388_2.png) [@derpycoder](https://forum.elixirforum.com/u/derpycoder)\
**Post date:** [December 18, 2022, 11:32am UTC](https://forum.elixirforum.com/t/phoenix-liveview-with-webassembly/52607/2 "2022-12-18T11:32:42Z")

</div>

In the talk on LiveView native, linked below, this point was raised towards the end.

A common core, written in rust perhaps, can be used to jump start anyone approaching LiveView implementation in any platform.

[![](https://img.youtube.com/vi/dnDGh_Jmw-s/maxresdefault.jpg "ElixirConf 2022 - Brian Cardarella - What is LiveView Native?") ](https://www.youtube.com/watch?v=dnDGh_Jmw-s&t=1800)

* * *

LiveView is not yet in version 1, so jumping straight to a static typed language without fleshing out the needs of users will just introduce unnecessary friction.

Also, WebAssembly has no direct DOM access, so despite its superior performance, you may find that it is slower than JavaScript for LiveView use case due to extra I/O overhead.

For this reason, currently people are finding most success with WebAssembly for algorithmic / compute-intensive tasks.

And for DOM stuff, LiveView will still need JavaScript, until [Webassembly Interfaces](https://hacks.mozilla.org/2019/08/webassembly-interface-types/) becomes standardised!

---

_[View the full topic](https://forum.elixirforum.com/t/phoenix-liveview-with-webassembly/52607)._