Linked by Thom Holwerda on Thu 18th Nov 2004 10:19 UTC
QNX I think that everyone reading OSNews will have heard at least something about QNX. You can regard this article as an introduction, but also as a review, and as a "Is-QNX-Ready-For-The-Desktop? article". To start off, I put together a short explanation of the merits of using a microkernel. Let me start off by saying that QNX Software Systems (QSS) does not aim towards the desktop with their Neutrino RTOS.
Permalink for comment
To read all comments associated with this story, please click here.
@ djm
by pkj on Fri 19th Nov 2004 15:09 UTC

I would not jump to conclusion that "QNX, being a RTOS, actually uses a simple O(1) scheduler." FYI: to addition to FIFO (typical RTOS) and Round-Robin (typical UNIX) QNX also provides sporadic scheduling:
http://www.qnx.com/developers/docs/momentics621_docs/neutrino/sys_a...
The question only if you use it or not, QNX itself does not care.

Again, there is an application-centric approach (desktop market) where a designer assumes that OS will take care of her/his application(s). Unlikely desktop market, majority of real-time & embedded products shiped as a whole system and you are in full charge of it but also you want (and you have) a full control of system modules, including predictably behaving RTOS. QNX is no exception to that.

It is simply wrong to acuse QNX in lacking desktop features: it is not meant to be a desktop. QNX is just a self-hosted system which allows embedded & real-time developers also prototype their algorithms/solutions/applications w/o real target h/w but still having native OS, not sort of emulated. This feature (sure among others, equally important) wins many designs for QNX. Vmware+[Windows|Linux]+QNX is quite usual setup for a commercial QNX developer.