Stdlib criticisms come up a lot, but it bears mention, re-mention, and re-re-mention that Nim programs need not be as dependent upon its stdlib as many other languages by design. Go has no generics (yet?) except weird special case things and Python needs C extensions to be at all performant which are a different skill set (though Cython makes it much easier).
Nim is more like C++ where performance/feature-sensitive people can/often do just replace/avoid the C++STL. The stdlib is just one pool of implementations..granted likely the first one new Nim programmers see. With data structures, there is never a perfect one for _all possible_ use cases..Use cases must be restricted first and there are many ways that can happen. Restrictions that specialize then afford optimization opportunity. So, if an "early lesson" in Nim is that maybe you have to hunt down a package for a DS or roll your own, that is not actually such a terrible outcome. Heck, in Ancient Times, you could just "cp stdlib/tables.nim myproj/" and start hacking away.
