Linked by Eugenia Loli on Mon 9th Oct 2006 01:31 UTC
Thread beginning with comment 169917
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-07-07
Hmm...I wonder how QNX would compare against VxWorks, for instance. Are they even comparable, for that matter?
QNX has a microkernel architecture. The QNX kernel contains only CPU scheduling, interprocess communication, interrupt redirection and timers.
VxWorks, on the other hand, uses a monolithic kernel including extensive intertask communications and synchronization facilities.
That said, they're fairly comparable from a developer's point of view.