Hello folks! This article on /. (boo, hiss, I know, but it is read by many) presents a problem looking for a solution. And Haskell may well be the solution. http://it.slashdot.org/article.pl?sid=07/01/30/1547235 I have already chimed in on the thread and I thought a few of you might also. Seems like the perfect opportunity for some friendly haskell advocacy since the people who read this article are more likely to be concerned about the future of software development and looking for a solution like Haskell. -- Tracy R Reed http://ultraviolet.org A: Because we read from top to bottom, left to right Q: Why should I start my reply below the quoted text
Hundreds of cores will bring that level of complication that dumping things onto declarative programming may turn out to be the only choice for the software industry. I am surprised they haven't started to prepare for that yet. Apparently their foresight remains the same as when their PhDs waited for Bill to reinvent DOS;-) Declarative programming however is not about glorious ideas but about reducing them all together. For the average sequential Joe logic programming is easier than lessons from aesthetics and thus simple tasks (e.g. without arrays) will be easier for him to commit to OR-parallel Prolog. Then beyond Prolog there is linear logic programming which has the same feel but brings concurrency, constraints and agents by definition. Haskell should remain for the chosen dozen:-) Cheers, --Andrzej
The only thing your'e gonna get from /. is a watercooled alienware box on rails... And a gazillion of inane comments on the metasubject whose CPU is bigger.
participants (3)
-
Alexy Khrabrov -
Andrzej Jaworski -
Tracy R Reed