As Nim is approaching maturity in the public eye,

I claim that as a language, it has been mature for a long time.

However, in terms of documentation and standard lib, it hasn't been.

For the end user of the language, when you try to solve a real world problem, 
in this regard it is still immature.

It doesn't handle all the use cases that a user wishes to do with a language. 
Which are the areas most lacking?

Users can get stuck for lack of documentation, for lack of examples, for lack 
of functionality for a particular use case, or just a whole use case area that 
is simply unsupported.

What were you recently trying to solve, where you got stuck or was unclear 
about how to approach or advance with the available Nim resources?

What are the confusions, and which domains Nim doesn't have anything to show 
for?

I think surfacing these issues will let us see clearly what is missing, and 
prioritizing better.

Too often language fans attempt to see the issue from a boss point of view, or 
from acceptance or stability guarentees point of view, where really sometimes 
users leave or stay in a language, simply for being able to provide them with a 
quick way to get things done.

Nim is the best programming language I know, so let's make it obstacle free.

Please discuss :-) 

Reply via email to