Slashdot Mirror

← Back to Stories (view on slashdot.org)

New Languages Vs. Old For Parallel Programming

Posted by timothy on from the nothing-new-will-ever-happen dept.

joabj writes "Getting the most from multicore processors is becoming an increasingly difficult task for programmers. DARPA has commissioned a number of new programming languages, notably X10 and Chapel, written especially for developing programs that can be run across multiple processors, though others see them as too much of a departure to ever gain widespread usage among coders."

1 of 321 comments (clear)

  1. Bad idea by junglebeast · · Score: 0, Redundant

    Creating threads is extremely easy to do in Java, .NET and C++. We don't need "inherit" parallelism in every loop where the performance gains are negligible. The programmer knows best. The programmer can synchronize more efficiently and divide tasks more efficiently than any automated "parallelizer" ever will, and having such automated retarded languages will only reduce overall performance when you have lots of applications running, all of which might as well have been sequential, but are now all fighting for multiple cores.