opendylan VS Nim

Carp, Lux and Dale are 3 I'm familiar with.There's also Dylan, though that one dropped its parentheses. But if we go by the brackets, technically, we can argue that any expression-based languages is a Lisp. I once wrote a Lisp to JS transpile whose output had more parens than the input. :)

Julia is a Lisp in the same form as Dylan.

I really wish they would fix the static linking. has needed a hack for three years:

https://github.com/nim-lang/Nim/issues/15220

The comparison of Yaksha to Python and the niche it occupies remind me very much of Nim: https://nim-lang.org/

closes #16654; add a test case.

https://nim-lang.org/

remove legacy code; the first iteration now can build Nim with cpp backend

Rust is increasingly beginning to be integrated into Linux Kernel Modules, Android, and even Ruby's new YJIT. C served it's purpose, but it should not be used anymore due to all of the security vulnerabilities it has allowed over the decades. Use Go, Rust, Crystal, Nim, Zig (no GC), or even V (no GC) instead, literally anything besides C/C++. If you still insist on continuing to use C/C++ for new projects, you are taking an unnecessary risk and potentially putting other users or your employer's security at risk.

One unusual hurdle for Nim right now is that on Windows, many of the anti-virus vendors out there are overly aggressive in flagging as bad any executable that was written in nim [1].

Don't know if they've made much headway lately, but for awhile even the main installer was getting flagged, as well as tools like choosenim.

See e.g. https://github.com/nim-lang/Nim/issues/17820

My guess: Nim doesn't like to deal with procedures which have very similar name, read: bug, https://github.com/nim-lang/Nim/issues/21272 You could try to change the names of procedures to more distinct.