←back to thread

Nim 2.2.6

(nim-lang.org)
159 points xz18r | 2 comments | 31 Oct 25 14:15 UTC | HN request time: 0s | source
Show context
synergy20 ◴[31 Oct 25 14:45 UTC] 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 ◴[31 Oct 25 15:24 UTC] 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 #
cenamus ◴[31 Oct 25 15:40 UTC] No.45773309[source]▶
With hard fork do you mean the 2.x.x version?
replies(1): >>45773395 #
tinfoilhatter ◴[31 Oct 25 15:47 UTC] No.45773395{3}[source]▶
Apologies for not providing a link!

https://github.com/nim-works/nimskull is the hard fork I was referring to.

replies(2): >>45774692 #>>45778278 #
1. Intralexical ◴[01 Nov 25 00:45 UTC] No.45778278{4}[source]▶
Last non-bot commit was over 2 weeks ago, and it seems to be mostly 1 account working on it. I don't think it looks active enough to be the big schism it's made out to be?
replies(1): >>45778786 #
2. tinfoilhatter ◴[01 Nov 25 02:28 UTC] No.45778786[source]▶
Nim itself has very few core developers. Comparing the number of developers involved in a hard fork to the number of Nim developers is silly, in my opinion at least.

The project has 21.5k commits authored, most of them oriented at replacing the existing compiler backend with a CPS-oriented one. Nim 3.0 is replacing the backend with one that is focused on CPS. There is no doubt that the developers responsible for the hard fork of Nim inspired Nim 3.0.

Yes, it very much is the big schism it's made out to be. I don't know what kind of activity level you expect, when the Nim language itself has few core developers working on it.