News for hackers. Stuff that matters.
Re:Ray Tracing in Nim by mhh__ on Wednesday July 01, 2020 @11:39PM (#23709732)
Is that not true of almost any other systems language (depends if you count Go as a systems language)?
Re:Ray Tracing in Nim by beagle3 on Thursday July 02, 2020 @03:28AM (#23710801)
Nim still Mostly retains its pythonic nature (fun and readable) even when you do whatever’s needed for C/C++ level performance.

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

Re:Ray Tracing in Nim by mhh__ on Thursday July 02, 2020 @09:56AM (#23713117)
I've been paid to work on D so no need to preach to the converted. I'll have a look at Nim too.
Re:Ray Tracing in Nim by entha_saava on Thursday July 02, 2020 @05:36AM (#23711496)
> Rust feels like a court filing.

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.

Re:Ray Tracing in Nim by mratsim on Thursday July 02, 2020 @05:34AM (#23711490)
It depends. On current CPUs the bottlenecks are in order:

- 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).