Yes, but Go got Google at its back, and it made a huge difference. You either have a successful community, or a big entity, otherwise it's hard to have an ecosystem that is good enough for serious usage
I'm inferring from the list of languages you described above that you're doing a lot of line-of-business applications where, yeah, it's almost essential to have that huge, Java or Python sized ecosystem.
Nim doesn't have that. But Nim isn't really aimed at that kind of work, either. What it does have is very good C/C++ interop, which means that it's easy to interface with existing low-level libraries. That makes it a pretty decent option for writing low-level bits, or looking to incrementally migrate from C/C++ to something a bit more modern.
For the mostly-Java stuff I'm working on, I rather wish the native components were written in something like Nim. They'd be easier to maintain if they were.
Sure, you can bootstrap something really quickly in Python and Nim, but when it comes to creating beefy APIs, I find that Go offers a much shorter development cycle. Sure it is slightly more verbose, but when your code compiles it usually works (which is partly due to the way Go deals with errors). If you need to handle a large number of requests, scaling with Go is a breeze and a nightmare in Python.