I have used Nim extensively and done a lot of metaprogramming in it. The biggest risk to metaprogramming is that it allows crazy syntax that you have to learn s

I have used Nim extensively and done a lot of metaprogramming in it. The biggest risk to metaprogramming is that it allows crazy syntax that you have to learn separately. Nim does very well here to enforce limitations which work well in reducing this risk. Comparing Nim's metaprogramming to Rust's shows what I mean. In Rust you can write macros that act on token streams, so as long as the token stream is valid it can be used. This allows libraries like the typed-html package[1]. In Nim you cannot do this unless you put the HTML in a string literal. This limitation created a syntax that is far more idiomatic, admittedly at the expense of familiarity for users of HTML: buildHTML(): html(): head(): title: text "My webpage" body: p(class="red"): text "Hello World" In my experience this works quite well, you can see a larger example in our Forum's code which is written using a SPA framework called Karax[2]. Please don't let style insensitivity discourage you from using this wonderful language. 1 - https://docs.rs/typed-html/0.2.0/typed_html/ https://docs.rs/typed-html/0.2.0/typed_html/ 2 - https://github.com/nim-lang/nimforum/blob/master/src/frontend/threadlist.nim#L116-L155 https://github.com/nim-lang/nimforum/blob/master/src/fronten...