Linked by Thom Holwerda on Thu 18th Aug 2005 16:46 UTC, submitted by Nicholas Blachford
Intel "At next week's Intel developer forum, the firm is due to announce a next generation x86 processor core. The current speculation is this new core is going too be based on one of the existing Pentium M cores. I think it's going to be something completely different."
Thread beginning with comment 20000
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: I've heard.....
by CPUGuy on Fri 19th Aug 2005 12:27 UTC in reply to "I've heard....."
CPUGuy
Member since:
2005-07-06

Well, really, had BeOS been developed all this time it really would be the perfect OS for this. The API forces programmers to use mutliple threads in the applications. So every application that has ever and will ever be in existance for BeOS supports multiple processors.

Reply Parent Score: 1

RE[2]: I've heard.....
by nimble on Fri 19th Aug 2005 12:51 in reply to "RE: I've heard....."
nimble Member since:
2005-07-06

The API forces programmers to use mutliple threads in the applications.

How did it do that? Did BeOS terminate your application when it didn't spawn a new thread for a couple of seconds or something?

Seriously, all an API and OS designer can try to do is to make multi-threading as convenient and efficient as possible.

Reply Parent Score: 1

RE[2]: I've heard.....
by Givas on Fri 19th Aug 2005 17:18 in reply to "RE: I've heard....."
Givas Member since:
2005-08-19

Well, really, had BeOS been developed all this time it really would be the perfect OS for this. The API forces programmers to use mutliple threads in the applications. So every application that has ever and will ever be in existance for BeOS supports multiple processors.

Having multiple threads for apps, windows, input devices, etc. is good for GUI latency, but it does not help much if you want to watch a movie, for example. In BeOS (almost) all algorithms doing real work are sequential and this is in no way different to Windows and Linux. Parallelizing those algorithms is very difficult and error-prone, when using C++. Also, hardware-threading is too heavy-weight for massive concurrency (tens of thousands of threads).

Forget BeOS; it does not at all make writing parallel algorithms simpler. Instead, use a programming language that is made for concurrency. Intel should also have a plan how to make software utilize their cores.

Reply Parent Score: 1