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):
more mature than zig, much easier than rust.
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.
https://github.com/nim-works/nimskull is the hard fork I was referring to.
A hard fork with a goal of being incompatible _sounds_ more strong behaviour on the part of those who forked, than on the original language owner.
I’m sure there’s a lot of context I’m missing. But what is the story behind this?
There was a falling out between the Nim core development team and several volunteer compiler developers. The former seemed to be paying more attention to their personal projects, while still desiring to maintain their positions of control and authority over Nim and its direction. The latter group grew increasingly frustrated, the situation became extremely toxic, and ultimately Nim lost several talented compiler developers to the hard fork.
I believe the goal of being incompatible with Nim resulted from the developers involved in the hard fork feeling like the Nim development team had done a poor job of designing certain portions of the language and compiler. I'm pretty sure they ditched the C++ backend, and made some substantial changes to the langauge to bring it more inline with their ideals.
I'm not involved in the development of either project, so a much better source of information would be the Nimskull project's developers themselves and the core Nim development team.
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.