Nim dev here.
If you are talking about async/await:
- for concurrency it has been in the standard library for a couple of years. Also you can implement it as a library without compiler support.
- for parallelism, Rust is in advance. Nim has a simple threadpool with async/await (spawn/^), it works but it needs a revamp as there is no load balancing at all.
You can also fallback on the raw pthreads/windows fibers and/or OpenMp for your needs or even OpenCL and Cuda.
Regarding the revamp you can follow the very detailed Picasso RFC at https://github.com/nim-lang/RFCs/issues/160 and the repo I'm currently building the runtime at https://github.com/mratsim/weave.
Obviously I am biaised as a Nim dev that uses Nim for both work and hobby so I'd rather have others that tried both comment on their experience.
In Async-await on stable Rustnim-lang
RFCs
OPEN SOURCE2019–2025
nim-lang / RFCs
RFCs
A repository for your Nim proposals.
31Distinct people
53Mentions
2Explicit recommenders
143GitHub stars
What to know before exploring
What it is
A repository for your Nim proposals.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Nim has been on a steady path of improving tooling support[0] since 2.0 release. LSP is a lot more stable now than even a couple months ago. That's what I love from…
archargelod used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- mratsim/weave · linked in 5 of the same discussions
- nim-lang/nim · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year53 dated mentions
Observed mentions: 2019-01-09 14:38:56 UTC to 2025-12-05 18:00:03 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 5 | 2 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 15 | 0 | 15 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 13 | 3 | 10 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
RFCs
A repository for your Nim proposals.
Which RFCs are being implemented?
Check out these milestones for the list of RFCs that are planned to be or are currently being implemented: #503.
Contributing
Submit a new, appropriately named issue based on issue form.
Read the full README on GitHubWhat Hacker News says
5 sourcesDesigning a Multithreading Runtime for Nim – Project Picasso
9 points · Open discussionLinks for anybody who doesn't know what is being talked about here, https://github.com/nim-lang/Nim/wiki/Destructors,-2nd-editio... and https://github.com/nim-lang/RFCs/issues/144 describes the specification for those changes.
The plan AFAIK is to ship it with v1 but it would not be default and you would need to do `--newruntime` for using these features. As they stabilize over time and things get ported to this new runtime, it would be made the default.
In Nim 0.20.0 (1.0 RC1) releasedProposal to add 'owned' refs to Nim
2 points · Open discussionActually plenty of issues are RFCs and feature requests.
We have a new RFC repos to brings a bit more sanity to the bug tracker: https://github.com/nim-lang/RFCs/issues
In Nim in 2018: A short recap