←back to thread

Nim 2.2.6

(nim-lang.org)
159 points xz18r | 1 comments | | HN request time: 0s | source
Show context
synergy20 ◴[] No.45772525[source]
nim is memory safe, python syntax, emits c/c++/js. It really deserves more love and publicity.

more mature than zig, much easier than rust.

replies(5): >>45772662 #>>45773011 #>>45773084 #>>45773138 #>>45777708 #
tinfoilhatter ◴[] No.45773084[source]
It's too bad that the BDFL of Nim (Araq / Andreas) treats the language like his personal compiler development playground. This has led to a hard fork of the compiler, many experienced and frustrated developers leaving the community and language behind, and an extremely fragmented ecosystem.

He is also very difficult to work with and isn't very welcoming to newcomers. The community "leaders" / moderation team is also full of abrasive individuals with fragile egos.

replies(11): >>45773309 #>>45773547 #>>45773578 #>>45774278 #>>45774745 #>>45775652 #>>45775816 #>>45777119 #>>45777255 #>>45778879 #>>45778930 #
1. Ancapistani ◴[] No.45778879[source]
> He is also very difficult to work with and isn't very welcoming to newcomers.

This hasn't been my experience at all.

When I first tried Nim, years ago, I came across an inconsistency in a database connector in the standard library after only a couple of weeks. I pinged him to ask if I was understanding it correctly and confirm it was a bug. He agreed it should be updated, so I put together a pull request. It was reviewed quickly, we went back and forth a couple of times over some details, he asked me to include some documentation updates, and it was merged without issue in a couple of days in total.

Given that I came to the language as a complete newcomer and had commits to the standard library less than three weeks later with the BDFL's approval, I simply can't agree that he's difficult to work with or not welcoming.

YMMV, obviously.