KubuS

The comparison of lazy evaluation to washing dishes just rocks!

Way to costly for me too.

spivonious is right, this was all basics - nothing new here, really.

If a developer does not know about locks/deadlocks etc. then I'm sorry to say, but he/she is just a poor developer. This is first year's knowledge on any decent university, no major degree required. This story was good maybe for Channel8, not 9.

I can't say for all the niners, but I personally feel that we should focus on specialized tools that assist in debugging concurrent programs, rather than stating the obvious about problems in parallel programming.

nothing interesting in this video, sorry.

Very nice And the part reading a developer guide is just awesome. I hope someone in MS will come to realize that naming things in a more consistent way is REALLY important.

I've been waiting for it too. Now I can't wait for the details to be announced on PDC

I supprot Johannes in that unordered results should be the default.

TPL and PLINQ should abstract away implementation details of parallel programming (as they do), but shouln't abstract the notion of parallel computing, which in its nature is unordered.

Nobody complains about SQL not preserving results ordering by default. SQL is set based in terms of data, and parallel computing is in a way set based in terms of Tasks. We shouldn't fool developers into thinking that parallel programming is the same as sequential programming, because ideas behind them are quite different and developers need to be be aware of that fact.