Live data from Hacker News

Nim 2.2.6

nim-lang.org

81–90 of 98 posts

Re: Nim 2.2.6

#81

Earlier quoted context omitted.

Actually, that’s not far from the truth. The reasons are: Lack of contribution. If someone isn’t doing actual programming work, doesn’t have time management to maintain libraries, or isn’t contributing successful applications, it’s hard to take constant criticism seriously. Only showing up to complain. Some people disappear for months and then reappear only to complain about design decisions, like "Why were multimeth…

Are you suggesting that the reason Nim isn't successful is everyone else's fault, and that the Nim development team and community aren't responsible for its trajectory? I'm sorry, but not many people are going to want to use a programming language when they're mocked or insulted for simply asking questions. Nor are many people going to want to use a language where the core development team focuses on shiny new things…

[flagged]

Re: Nim 2.2.6

#82

Earlier quoted context omitted.

> language like his personal compiler development playground re personal compiler development playground: I don't see this for Nim 2. Nimony/Nim3 is more of a "playground", but rightfully so: he is creating a new major version of the language and aiming to improve the architecture of the compiler. > He is also very difficult to work with and isn't very welcoming to newcomers I don't have full context on the drama beh…

> re personal compiler development playground: I don't see this for Nim 2. Nimony/Nim3 is more of a "playground", but rightfully so: he is creating a new major version of the language and aiming to improve the architecture of the compiler. Araq likes to work on the shiny flashy things he finds fun / interesting to work on. I'm not going to fault him for that, but things like atomics on Windows are still broken. Peopl…

[deleted]

Re: Nim 2.2.6

#83
post #49

Earlier quoted context omitted.

> The community "leaders" / moderation team is also full of abrasive individuals with fragile egos. I certainly hope this isn't the case any longer. As one of the moderators I feel the current group is very patient and welcoming. At least that's what we're trying for, no one is perfect so I'm certain you can find counter examples. But as a whole I think we're doing pretty well. If you have any specific complaints we…

It makes sense you feel that way, as you're one of the moderators. I feel quite differently. Thanks for the offer, but there's a reason why Nim hemorrhages users as fast as it gains them, and a big reason for that, IMO, is the toxic community which definitely includes the moderation team.

FWIW, I agree that Araq is an abrasive character and probably not a great community leader for an open source project.

But I disagree with your take on the moderation team. I don't know if you have specific names to call out, but PMunch, miran and the rest of the team have been nothing but welcoming, in my experience.

Re: Nim 2.2.6

#84

Earlier quoted context omitted.

Are you suggesting that the reason Nim isn't successful is everyone else's fault, and that the Nim development team and community aren't responsible for its trajectory? I'm sorry, but not many people are going to want to use a programming language when they're mocked or insulted for simply asking questions. Nor are many people going to want to use a language where the core development team focuses on shiny new things…

[flagged]

[flagged]

Re: Nim 2.2.6

#85

Earlier quoted context omitted.

> other than very robust metaprogramming lol then i guess zig's comptime isn't a "whiz-bang-pow killer feature" either

Metaprogramming isn't exactly new. I guess the novelty is that its history in the systems language space is spotty, and has only recently become usable in the way a Lisper might want to use it.

> Metaprogramming isn't exactly new

My guy what exactly do you think comptime is? More to the point: what exactly do you think metaprogramming is...?

Re: Nim 2.2.6

#90

The main release note here is more stable async. I’m curious how folks using nim feel about the async situation. One of the most recent opinions from the discord is: “ we have async and asyncdispatch but its leaky and bug prone esp when used with threads and causes deep ownership issues, i prefer using taskman when possible but it leaves the IO problem yet unsolved ” I’ve also been told to just use regular threads wh…

As one who was interested by Nim and tried it out for some personal projects, I found that this was the biggest problem with the project. There's several options for any given need (including internal tools like LSP or installing the compiler) with very little clear way to choose between them. Each will have different (dis)advantages that you must discover primarily by digging through forum posts or GitHub issues.

In some ways it's the sign of a very strong language, like the curse of Lisp: someone can easily just write their own version of whatever they need. But as a user trying to navigate the ecosystem it is frustrating. I do keep meaning to try it out again though; the language itself is very pleasant to use.

Post reply on HN