Hacker News Reader

Comment by farseer | Hacker News Reader

With linux options in embedded space aplenty, who would want to move to a propriety os? QNX's big brother Vxworks has already been pushed out of most consumer embedded devices and is now limited to space probes and critical medical equipment. I just don't see a future for QNX anywhere.

View on HN

Dealing with Linux can be a PITA. Once you get a base system up you still need to roll a bunch of our own stuff. Do you use System unit or systemd, etc. The driver api's are pretty unstable.

I make embedded linux device and I'm curious if QNX could make things easier, especially for long term stability.

Not everything has to be linux. It's good to have options for avoiding monoculturalization.

It's not a real option (to Linux) though at it is still governed by a non-free license.

not everyone cares about that. They want something they know and something that works for them, not everything has to be FOSS

For real-time systems, QNX should be compared to FreeRTOS, CMSIS/RTX, VxWorks, or, if you after the new cool stuff, Zephyr, perhaps, but not Linux.

> but not Linux.

I disagree. Linux merged the real time stuff (https://news.ycombinator.com/item?id=41594862) not so long ago so it's now a real-time capable kernel, and hence it should be held comparable to other real time kernels.

Good luck certifying an automotive or an industrial system that can lead to loss of life or severe disruption if it malfunctions. As far as I am aware, QNX, VxWorks, and CMSIS have all been used in systems that passed certifications. As IoT &co. get applied more broadly in our society, they are put in more places where they are expected to function flawlessly. I would rather want my power grid or water utility operator to use CMSIS, for example, than rt-linux.

The only serious user of rt-linux which uses it to build a hard-RT system that I know is SpaceX. Look up the Reddit AMA post from them on how rt-linux is used. They are staying on a specific kernel version, had to do kernel patches (other than applying rt-linux), they use a very specific model of an old Xeon for low latency interrupts, incorrect programming of one process can disrupt the RT behaviour of another process, and most importantly, they have a secondary board, a truly real time one (PowerPC based, IIRC) to communicate with the real hardware.

One interesting morsel in all of what you described is that for all of the hoop-jumping SpaceX does to bolster rt-Linux, it is -still- easier/faster/ better by some business metric for them than the alternative.

If the redundant hardware and some ground rules they have in place have made the onboarding of developers better and faster, than perhaps it should be recognized that they seem to be prioritizing the DX - especially since plenty of applications in RT will also use redundant hardware and confine their hardware selection similarly to prioritize the performance targets of their application, SpaceX just added developers to the feature matrix.

There's BSD too (e.g. Playstation, Apple Airport, Some POS devices and printers)

Reply on news.ycombinator.com