luajit2 VS asm-dom

And Neovim is using OpenResty's branch of Luajit

Yea, LuaJIT can get near C speeds, as far as I'm aware. You can read more here: https://luajit.org/luajit.html

I also found this gtihub repo, this one is using luaJIT a just in time lua compiler, i dont know if you have any python expirience but this one, but from what i understand luaJIT makes lua a language that can be compiled and run in your terminal, it aperently also has a comminty made package/library manager called cherry.

openresty's LuaJIT2 has, and makes, regular releases (the last one was less than a month ago), and closely tracks development, including the extensions beyond Lua 5.1.

There is also the openresty fork of luajit which Neovim can be built with and provides their own releases.

luajit.org said

Remember, bad C++ code will certainly be slower than good code written in an interpreted language! That being said, Lua is very fast, one of the fastest scripting languages. See this thread, which talks about LuaJit.

https://github.com/openresty/luajit2

It has a few extras but they agree with the original luajit authors opinion that not every 5.2 feature can be made in jit.

Aside from Blazor there's already some other projects like Yew (rust), seed (rust), asm-dom (C++) and vugu (Go) and more that have decent followings and activity. A lot more (especially managed languages) are waiting for some features to come online like wasm GC and host bindings (direct wasm access to browser apis which includes the DOM). It'll take a bit of time, but it'll get there eventually.

FWIW if you look around, C++ and Rust libraries for DOM manipulation exist (I haven't searched for other languages which compile to WASM):

https://github.com/mbasso/asm-dom

https://github.com/sycamore-rs/sycamore

I think solving the problem of DOM access on the library level is exactly the right way to tackle this problem. The library user don't need to care about specific WASM features, and the library implementation can be simplified when those WASM features become available (and also implement per-browser fallback paths)

Wasm is already around for a while. There are probably some libs to access the dom and frameworks around that wrap the js part completely Found this after a short search https://github.com/mbasso/asm-dom Also Blazor seems to work fine, but didn't really test it beside playing around a little bit with it

Thanks for the kind words! :-) Yeah, you've got a good description of the use case for it. You give me too much credit though. :-) It's built on top of Emscripten, which handles a lot of the low-level bindings between C++ and the browser. Also, asm-dom helps fill in a big gap between C++ and the DOM.