New Languages Vs. Old For Parallel Programming
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."
You are a giant douchebag
The "apocalyptic evangelical christian mindset" is clearly evident in PERL.
It is completely inconsistent, unpredictable, illogical, and quite plain crazy. Unfortunately, it's a necessary evil, just like IBM, Microsoft, Windows, x86, FORTRAN, COBOL, SQL etc.
I recently wrote an asynchronous MySQL client library for a client, and wrapped it in Lua w/ a LuaSQL interface (not easily usable by others, however, because it's tied to the underlying event loop of the client's server.) It's actually fairly trivial, because MySQL is fairly trivial.
The reason it hasn't been done is because 99.99% of programmers are sheeple. And this sheep is now too busy to re-write the library for FOSS, since I'm finishing up an async-SPF library and will move on to greener pastures thereafter. Smarter sheep just use PostgreSQL, which has a very nice and simple async C interface.