> "Idiomatic Nim code is fast and Nim does not have "optimization walls." "
To me, the "... Nim ... and Nim ..." doesn't flow so well. What about "Idiomatic Nim code is fast and there are no "optimization walls" if you want to make it even faster." (even if it's a bit longer)? But I guess this can still be improved by thinking more about it. A question to @all : Do you think that "optimization wall" is understood by most people? As far as I'm concerned, without the context from this thread I would only have _guessed_ the meaning. @Stefan_Salewski , I think the point about tuned libraries is good. Whether we want to add this, too, depends on how much space we have. If we want to describe Nim with a few bullet points, I'd probably leave the library (dis)advantage out, on the other hand, for one or two paragraphs on Nim performance, mentioning the effect of libraries would be good.
