EXCELLENT! :D :D :D
A few minor nitpicks, which I hope will be taken constructively for future articles:
- The article's second paragraph implies that Nim has the compilation speed of Golang. This will be a turn-off for an informed reader, and cause for the rest of the article to be taken less seriously. Go was designed with compilation speed as one of the top (if not THE top) priority. Go chose to sacrifice many features, syntactic improvements, performance optimizations, etc - all for the sake of being faster off the starting line. Nim, on the other hand, specializes in syntax flexibility, features, metaprogramming (which particularly slows down compilation), and uses a separate C compiler to generate the final optimized binary. I think Nim is definitely on the right side of history (especially with future cloud-based compiler-as-a-service reducing all compilation time to imperceivable fractions of a second), but we cannot claim to be best at everything.
- "The resulting executables are tiny - a 'hello, world' compiles to around 150K in Windows." Ahem... But I guess that's still small compared to Go and Haskell... Binary sizes do matter, because with a cloud-based compiler-as-a-service transfering the resulting binary could be the most time-consuming part.
- It's unfair to say that Rust lacks GC. Any lower-level language can have GC via a memory management library. Rust is about half-way between Nim and C in syntax ugliness and developer productivity, but the performance gains are razor-thin (and on some platforms easily trumped by the choice of Nim's C/C++ compiler).
- The image used in this article could give a casual reader the wrong idea about Nim's syntax. Even through I'm horrible with graphics, in my Facebook days, I've always tried to come up with an appropriate image to go with the link / story. That, unfortunately, is very important on today's Internet, as the vast majority of people who see a link to your article will scroll past it in a second on their social media newsfeed, and their brain will only process the visual...
Again, I hope that these minor nitpicks don't distract from the overall positivity of my response to the article. We definitely need more exposure.
I'm particularly happy about emphasizing Nim's Python-like syntax (which gives us a huge audience to target) and describing Nim as "a mix of the best of many worlds". It's not about being faster than C, compiling faster than Go, being as productive as Python / Ruby, etc - it's about maximizing the "golden mean".