Linked by Thom Holwerda on Fri 19th Mar 2010 13:00 UTC, submitted by Jim Lynch
General Development "With chip makers continuing to increase the number of cores they include on each new generation of their processors, perhaps it's time to rethink the basic architecture of today's operating systems, suggested Dave Probert, a kernel architect within the Windows core operating systems division at Microsoft."
Thread beginning with comment 414534
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Programs aren't pervasively multhreaded, because the hardware and software platforms cause diminishing returns for the hours a programmer puts into the work.

So, we shouldn't make it easier to use resources in a more parallel fashion, because programmers aren't already doing it well.

Isn't that a bit of a chicken-and-egg situation?

By making it easier for the developer to make use of those resources, making parallel applications can become easier, as we'd see more of them being made. This idea is one of many to tackle that problem, this time by just getting out of the way.

Ideally, you won't end up needing to code for a bunch of cores, but will have the whole dev system, from the bottom up, making it easier to use many processes and threads than to not do so, making gains from having more of them as automatic as having a faster CPU is, today...but without using functional languages everywhere to do it.

Edited 2010-03-21 06:46 UTC

Reply Parent Score: 2