Linked by Thom Holwerda on Tue 26th Sep 2006 23:14 UTC
Intel Quad-core processors are only the beginning of what a revitalized Intel has to offer, the company's top executives said here Sept. 26. The chip maker will deliver in November its first quad-core processors - chips that incorporate four processors each - for both desktops and servers, said CEO Paul Otellini here, in an opening keynote speech at the Intel Developer Forum. The quad-core chips themselves will offer up to 70 percent greater performance in desktops and 50 percent in servers.
Thread beginning with comment 166046
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: The beginning of what?
by bogomipz on Wed 27th Sep 2006 11:58 UTC in reply to "RE[2]: The beginning of what?"
bogomipz
Member since:
2005-07-11

Hello Kitty ;)

The Be API not only encourages multithreaded code, it automatically makes each window run in its own thread. This means that any program that opens a window is multithreaded. Of course this doesn't help much if all the work of the application happens in the thread of its only window, but I believe apps on BeOS generally use these threads for user interaction only. This is in contrast to say Windows where I'm sure you have experienced menus and other GUI components hang when the app has alot of work to do.

In addition to that, the application in the linked video has two threads that only do rendering. This is application specific code and is possible on any modern OS, but I guess the BMessage centric API makes it easier to achieve. Someone with actual experience beyond reading a book on BeOS programming might be able to elaborate.

Reply Parent Score: 1

RE[4]: The beginning of what?
by mphipps on Wed 27th Sep 2006 14:39 in reply to "RE[3]: The beginning of what?"
mphipps Member since:
2006-08-21

bogomipz has the answer pretty well nailed. The multi-threaded nature of the windows makes porting apps from "traditional" architectures a pain, but makes your UI feel responsive even when the app is pegging the CPU. The window's threads are also higher priority than most apps, which helps some too.

I just finished multi-threading a linux app and I really missed the BeOS threading API... :-D

Reply Parent Score: 1