Things I Learned from ACCU 2010
retard
re at tard.com.invalid
Fri Apr 23 16:09:55 PDT 2010
Fri, 23 Apr 2010 06:23:22 -0700, Walter Bright wrote:
> bearophile wrote:
>> Walter Bright:
>>> OCaml has a global interpreter lock which explains its behavior.
>>> Russell didn't know why the Haskell behavior was so bad. He allowed
>>> that it was possible he was misusing it.
>>
>> You have just the illusion to have learned something about this. Trying
>> to read too much from this single example is very wrong. A single
>> benchmark, written by a person not expert in the language, means nearly
>> nothing. You need at least a suite of good benchmarks, written by
>> people that know the respective languages. And even then, you have just
>> an idea of the situation.
>
>
> Fair enough, but in order to dismiss the results I'd need to know *why*
> the Haskell version failed so badly, and why such a straightforward
> attempt at parallelism is the wrong solution for Haskell.
>
> You shouldn't have to be an expert in a language that is supposedly good
> at parallelism in order to get good results from it.
Why not? Do you think parallelism is simple to manage (efficiently)? No
offence but a total novice has zero understanding of e.g. threads or 3rd
party libraries. The best he can do is to come up with something using
the stdlib Thread classes. Usually it fails miserably due to deadlocks or
other synchronization issues with locks.
More information about the Digitalmars-d
mailing list