upvote
The real win with the compile-to-C strategy is embedded - a million embedded devices only publish vendor-provided (typically GCC) C toolchains.
reply
This is a great part of Nim. I started using it with ESP32's for 5+ years or so now. Nimony is even more ideal for embedded.

Great part is that Nim's stdlib networking was easy to port to esp-idf's lwIP based network stack. So you get access to production Nim libraries for lots of networking stuff, or async, etc.

reply
A lot of compilers nowadays compile to wasm, when you have wasm, you can compile to C.
reply
Wasm is great, but it's a terrible IR for C back-compilation if you have alternatives available IMO.
reply
Nimony still puts the C code in the .cache/ folder as nim does.
reply
what does this imply? are you saying it does in fact still actually "transpile" to C?
reply