Thank you for the thoughtful input and the real world data points. I've felt similarly to your colleague a lot, I tend to run into situations where I'm stuck and there's nowhere to go. Then it seams that Nim is creating more problems than it solves.
I think a good word that somes everything up is friction- adopting Nim has a lot of friction. * A compiler message you don't understand and can't find answers to * Tooling that has bugs with no obvious solution * Documentation that takes too much brain power to process * Abstraction leaks- such as when you have to worry about implementation details by adding pragmas * Feature inconsistencies, such as when the GC doesn't work for threads * Bugs, especially ones that don't seem to get fixed That's when Nim creates more problems than it solves. I agree- I think this is what scares people away. It didn't scare me away- I'm motivated by passion. Nim is Genius. But it's still painful, and more than can be expected from a pragmatist to handle.
