←back to thread

Nim 2.2.6

(nim-lang.org)
159 points xz18r | 1 comments | 31 Oct 25 14:15 UTC | HN request time: 0.247s | source
Show context
banashark ◴[31 Oct 25 21:59 UTC] No.45777167[source]▶
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 whenever possible.

Do others have more info or sentiments to share?

replies(1): >>45783919 #
1. b3morales ◴[01 Nov 25 18:15 UTC] No.45783919[source]▶
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.