October 19, 2006
Threading, Ruby, and Python
Larry posts his disappointment that Ruby isn't really multi-threaded, and is therefor not able to take advantage of multi-core architectures (not without spinning up multiple instances of the interpreter, that is). The comments to the post are even more interesting, pointing out that Python can have the same issue, and there's a lot of talk in the python community that what we think of as multi-threading is really a bad idea. Everyone agrees that you need to be able to perform operations in parallel, and leverage the hardware fully, but maybe shared memory and traditional synchronization mechanisms are just wrong, wrong, wrong.
Posted on October 19, 2006 at 09:48 AM | Permalink
The comments to this entry are closed.