Front-up disclaimer: I went into the being exited trap due to what Nim has to offer, too.
Re the OP issue: To promote a language one should first know what it actually is one wishes to promote. So: what is Nim at its core? What is _the_ definition/goal of Nim? Is it a system language or is it one targeting the web (js)? Or one that wants to address many niches? Whatever it is desired and decided to be, should be a clear and binding frame at least for some time (well beyond v. 1.0). It seems to me that to promote Nim we should have a clear, binding, and effective understanding of what it is meant to be because those to whom we promote it will check whether it actually delivers and whether they are interested. Side note to avoid misunderstandings: I do not care (anymore) what Nim is meant to be. But whatever the Nim masters decide it to be should be targeted _consistently_. It's no shame for a not yet mature language to not offer everything and the kitchen sink. It _is_ a problem, however, if what it _actually_ is (and develops into) seems to be more a question of what just happens to be of interest to its developers at any point in time than of growing and extending a well defined core. Moreover, before promoting something one should be sure to have in place what's needed for newly won users to actually use it. Re. tooling I feel that Nim is well equipped (modulo debugging and, but that's maybe just me being picky, editor support); nimble, c2nim, etc. as well as nimdoc are useful and working (some polishing is needed but that is not critical I think). As for documentation I will refrain from commenting as my view seems to be different from the whole universe. To put it bluntly I think that the question should not yet be how to promote Nim. The question should be _what_ we are to promote (a system language? A do a bit of everything language? The cool new web thingy, ..?.) and how a status can be achieved in which promoting Nim makes sense and seems promising. In other words, a Nim beyond, say, 0.7 that has clear contours, is _consistently_ evolving within those contours instead of being somewhat of a chameleon, and that targets actual and _practical_ usability for the very developers (read: not just the Nim team and insiders) it is promoted to. > But yes, either @Araq will make some tough choices, bite the bullet and > remove niche features or we won't ever get 1.0. I'm surprised to read that here (and Araq not angrily dressing you down) but: _100% ACK_. I also feel that that without certain changes Nim will be 0.3 in 2025 and have many more features and gadgets but not many more users.
