> What more does one want? As I said, as an individual the promise of performance coupled with elegant and legible code is a compelling reason to learn the language.
As an organisation, not so much. I'd be more concerned with: 1. Accessing a pool of experienced developers 2. Access to extensive training materials and code examples 3. A strong ecosystem of libraries with solid community maintenance 4. A strong track-record of successful high-profile projects in my problem domain 5. Ideally, the active backing of a major corporation like Google for Go or Mozilla for Rust. Currently, Nim can't offer any of these. So if I was writing my project for a paying client rather than for internal use, I'd simply grit my teeth and write it in something like Go. That's why I'm arguing that realistically, growth will have to be organic as the community builds. It's going to take time. That doesn't mean that growth couldn't become explosive once the foundation is laid. That's the way that exponential growth works - as the history of Python demonstrates. But as things stand, there's still a long way to go before Nim becomes a viable option for the typical business-critical project.
