The [recent blog post](https://nim-lang.org/blog/2017/05/25/faster-command-line-tools-in-nim.html) I wrot eon the Nim blog also explored performance and build times in D/Nim based upon a blog post on the D site.
In it you can see that D and Nim achieve similar speeds in that particular benchmark (with Nim being faster when using Clang, but slower when using GCC according to [this issue](https://github.com/euantorano/faster-command-line-tools-in-nim/issues/1)). What I found most interesting in that performance comparison though was how easy it was to write an optimal version of the Nim program - the standard library CSV parser was my first choice of tool and I didn't have to then dig around for more optimisations (like D's 5 steps to get an optimal version using things like "splitter" and "appender!") which says a lot about how well written Nim's standard library and the language itself is in my eyes.
