My 2ยข: The biggest thing needed in Nim right now is stabilization of the GC and async/threading features. Right now those are in flux and it causes a lot of confusion for developers [e.g. me] who've moved past tire-kicking and are learning how to write serious programs. The tutorials and reference manual say one thing, there are newer tech-notes that say differently, there are more GC modes than I can keep track of, they have different interactions with threading...
I totally understand why this is the case, and I'm not faulting @araq or anyone else. It reminds me of what I saw of Rust's progress pre-1.0 when I used to look in on it every few months. (Rust used to have a GC, and went through major language changes.) But I would like there to be a release of Nim that finalizes the new ARC/ORC mechanism, `lent` / `sink` syntax, async and threading libraries, _and updates the documentation accordingly_ before there's any push for massive adoption. (Oh, also, I'd like to see some flashing neon signs reading "NIM IS NOT PYTHON" in large friendly letters, where newbies are likely to read them. Because from skimming the syntax it's easy to make the assumption that Nim is to Python as Crystal is to Ruby, and we've seen the resulting confusion in this forum several times.)
