> So let's say that implementing your game in Nim instead of C++ means 20%
> larger binary sizes, 20% more RAM usage, and 20% more CPU/GPU usage.
There is no reason it would be. It's not like Python or Java. You can allocate
structures on the stack. You can allocate memory on the heap and do
> Nim with the C backend can never be faster than C.
What we are actually comparing here is _typical_ code written in C to typical
code written in Nim. There are many examples where Nim can win out:
* _Typical_ C code is often actually partly / mostly C++, which is [often
We should start thinking of programming language performance in terms of
economic costs. We can then use the same units (Dollars / Euros / Bitcoins /
etc) to compare all aspects of programming language choice.
When we say for example that "C is faster than Python", we really mean that
it's
