Yes, not to mention, when was the last time you heard someone call somebody else a nimrod? The 1940s?
It can't hurt and Nim is a short and memorable name. Realistically it will probably have very little impact (and the core devs likely know this). Whether Nim gains widespread adoption has a lot more to do with whether it can compete successfully with Rust, C++, or whatever is remotely similar to it. D, for example, has a really good name (the successor to C), but hasn't become heavily used in industry despite what advantages it does have and years of development.
Nim should follow the tooling around Go and just steal all of the good parts. I think Nim's main competitor is Julia. I'd focus on weaving Nim and RoboVM code together so one could leverage all the libs from Java/JVM while getting native performance.
It can't hurt and Nim is a short and memorable name. Realistically it will probably have very little impact (and the core devs likely know this). Whether Nim gains widespread adoption has a lot more to do with whether it can compete successfully with Rust, C++, or whatever is remotely similar to it. D, for example, has a really good name (the successor to C), but hasn't become heavily used in industry despite what advantages it does have and years of development.