In case you want to give it a spin, nlvm has had some wasm support for some
time now: [https://forum.nim-lang.org/t/3758](https://forum.nim-lang.org/t/3758)
there's a new llvm version in place since that post which should hopefully be
an improvement, but do let me know if you have any success or
I'm not sure I agree with these sentiments...
The JS backend gives Nim the potential to attract a whole world of developers,
who might not be exposed to the language otherwise. Not that I personally want
a bunch of JS devs shaping the future of Nim, but fortunately for us, the
language has sens
> Then WASM comes along and (although it's not fully baked yet) it seems that
> Nim's JS backend efforts are now somewhat less valuable...
Let's look at how big that "somewhat" actually is according to some specific
aspects of WASM vs JS in the browser:
* JS call performance: Calling JS from
This thread could use some pointless grumpy whining. (Or at least that's all I
can contribute right now.)
I'm wondering about the future of `nim js`.
Nim has invested considerable effort into the JS backend - time that could have
been invested into delivering a more competitive "product" with j
What's new is my answer. :P
I don't know, but this post already asked several months ago and 90% of post
wording is same, :/
[https://forum.nim-lang.org/t/4049](https://forum.nim-lang.org/t/4049)
Our plans for the future are more general but improve the support for wasm as a
side-effect:
* Make the language more agnostic to the used underlying allocators
(destructors).
* Introduce an optional code transformation that maps exception handling to
`if` statements.
* Make the tracing g
I went from Go and recently had an interest in Web Assembly, but I do not feel
that Go is particularly good for it, mainly due to the large binary size. So I
look around for a new language and Nim seems perfect for it, modern, fast and
makes even binary files even under the web.
Have I found so
