If you ask me, available good libraries **is** a Nim's killer feature when I choose it for project over some other technologies.
On other hand, Nim bears extremely AoU (amount of unexplainable) level that makes it a dangerous choice every time. It's just... Look. * When using **PureBasic** your chances to deal with inadequate bugs are rather negligible and mostly occurs during compiler updates, or when you do something outright dangerous like messing with stdlib internals. * When using **CoffeeScript** you may encounter a lot strange things, but there is a catch - 90% of them are described in manual. Most of unexplainable things roots from engine differences or obviously stupid stuff like subtracting arrays from strings. * When using **Boo** / **C#**... Well, wonky things will happen, especially when dealing with GUI and async stuff. Unless you watch stackoverflow religiously, you may or not be doomed, since MSDN coverage is lacking at best. * Now, **Nim**... _Sigh_... Where should I start ? There will be roadblock bugs that happens 1 /5 time. GC will crash your code without any messages. Using cyrillic letters will crash your terminal IO unless you know it already. Etc, etc, etc... Most of time you **will** regret using Nim any time you hit something, which is like every 100 lines of code.
