What I like about Nim is that you can always get C performance if you just spend a little time. You can always use a profiler you like (I use vTune) to get to the hot loops and fix them.
See my post here: https://forum.nim-lang.org/t/5363#33576
See my post here: https://forum.nim-lang.org/t/5363#33576
I think it’s exceptional in that it feels lightweight while delivering great performance, and it has no “glass ceiling” of any sort.
Rust and D have no ceiling either; but D feels like a better C++ and Rust feels like a court filing.
D is definitely under-appreciated if you prefer C feel to Python feel
But HackerNews and Reddit told me that rust is very ergonomic after two weeks and if you do something in other languages that you can't do in rust, you are doing it wrong and it needs to be fixed.
- IO processing
- Memory
- CPU
In particular, any language that doesn't have any escape hatch to do manual memory management will have troubles to optimize memory bound workloads.
In scientific computing, machine learning, deep learning and in image processing, in particular stencil code, 90% of the workloads are memory bound (the CPU-bound being those involving convolutions and matrix multiplications once you get the data at its proper place, and things involving exponentiation or trigonometric functions).