IIUC, the diff b/t go and most languages is that go spawns threads through a slicing mechanism to leverage multiple cores, right?! That's why the go version sp

IIUC, the diff b/t go and most languages is that go spawns threads through a slicing mechanism to leverage multiple cores, right?! That's why the go version speeds up when run on multiple-core systems...right? So, I added pthreads to the ray-tracer program: http://pastebin.com/6V5JYyZG http://pastebin.com/6V5JYyZG Included in the paste are the execution times on my lowly dual-core laptop. Spawning more threads speeds up the program. I would be curious to see how it scales to more cores on modern CPUs. If you have a chance, won't you please give it a try on your system and let me know how changing the number of threads affects execution time? For anyone who wants to try pthreads in C, the simplest example and progressions I could find were here: http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.html http://cs.gmu.edu/~white/CS571/Examples/pthread_examples.htm...