Linked by Thom Holwerda on Sun 2nd Dec 2007 22:41 UTC, submitted by Amit Bahree
.NET (dotGNU too) "With all the modern systems using multi-core and multi-processor systems, tapping this new power is an interesting challenge for developers. It also fundamentally starts the shift on how your 'average Joe' interacts with a computer and things that he/she expects to be able to. First, check out the 'Manycore Shift' paper from Microsoft. Second checkout the Parallel Extensions to .NET 3.5 which is a programing model for data and task parallelism. It also helps with coordination on parallel hardware (such as multi-core CPU's) via a common work schedules. There is also a new Parallel Computing Dev Center on MSDN. Before you download the December 2007 CTP, make sure you have the RTM bits of the .NET 3.5 runtime. There are also a number of bugs fixed in this new CTP. If you want a quick introduction then check out a few videos available."
Thread beginning with comment 288075
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Another framework. Great
by jayson.knight on Mon 3rd Dec 2007 13:12 UTC in reply to "Another framework. Great"
jayson.knight
Member since:
2005-07-06

"The .NET framework is on version 3.5, while the CLR is still stuck on 2.0."

The CLR version is the same as the .Net version: http://msdn2.microsoft.com/en-us/library/ms230176(VS.90).aspx This is because .Net is the umbrella term for CLR + BCL + CLI (actually, the CLR is MS's implementation of the CLI). Regardless, we are now on v3.5 of the CLR.

"-Do not use locks."

For non-functional languages, locks are an (if not THE) imperative part of multi-threaded application design, unless you want race conditions and deadlocks all over your application.

I'd also love to know what these performance problems are that you speak of. It has been shown on numerous occasions that a properly designed .Net app has performance approaching that of unmanaged code.

Edited 2007-12-03 13:13

Reply Parent Score: 3

jayson.knight Member since:
2005-07-06

OSNews: Your URL parsing is munging the above URL b/c of the end paranthesis around VS.90.

Reply Parent Score: 4

Vanders Member since:
2005-07-06

For non-functional languages, locks are an (if not THE) imperative part of multi-threaded application design, unless you want race conditions and deadlocks all over your application.


Not if you're using message passing. I'm not going to claim that locks are not required at all, but good design and message passing can help eliminate them.

Reply Parent Score: 2

jayson.knight Member since:
2005-07-06

"Not if you're using message passing."

By message passing, does that mean serialization in the Java/.Net world? If so, that introduces a whole new set of problems and ramifications...

Reply Parent Score: 2