I always liked their original UI - Photon[1][2]. Very lightweight and fast. Also a distinct and consistent style. I understand why they dropped it in favor of Qt and later Web technologies, but it's still a big loss.
Glad to see QNX still progressing. I worked there as an intern twice in Ottawa and they're pretty damn good. Great place to work imo. I met some of the kernel devs there. Had the priviledge of working with one and he taught and demoed some of the kernel features to me. They gave us interns a full summer course on kernels, C programming, OS and some hardware. Fun times.
And none of them can hold a candle to QnX. I've used a whole raft of them and QnX stands heads and shoulders above the competition. The consistency of the implementation is extremely impressive.
It was mind blowing at the time because Linux required at least 4-5 floppies to set up a text-only base system while QNX ran live from just a single 1.44MB.
Photon microGUI was included in that, and it blew my mind that you could literally kill and restart Photon without disturbing any of the GUI apps that were still running.
They also mailed a manual along with the demo disk, and I was amazed that QNX had built-in network bonding, amongst lots of other neat features. At the the time I was using Slackware & the linux kernel version was still 1.x, I don't think bonding came to linux until 2.x?
Photon was what I was hoping for before I clicked the link. One of my favourite GUIs, closely tied with CDE.
Photon or not, I hated the period where they sort of moved to canned BSP deployment only, where in 6.5 I could just develop on a live system. This is nice.
Me too, although it's been a long time since Photon.
"This environment runs as a virtual machine, using QEMU on Ubuntu. To try the image, you'll need: Ubuntu 22.04 or 24.04." So it doesn't boot on bare metal?
Maybe they're trying to get away from needing Windows. The previous recommended development environment was cross-compilation from Windows.
The big news here is that they have a reasonable non-commercial license again.[1]
The trouble is, QNX did that twice before, then took it away.[2] Big mistake. They lost their developer base. Support of open source tools on QNX stopped. As I once told a QNX sales rep, "Stop worrying about being pirated and worry about being ignored".
They'll need to commit contractually to not yanking the non-commercial license to get much interest.
QNX should be licensed like Unreal Engine. If you ship enough products using it, it gets noticed and they contact you about payments, and if you're not shipping much product, Unreal doesn't care. This has created a big pool of Unreal developers, which, in turn, induces game studios to use Unreal. Unreal's threshold is US$1 million in sales.
Apparently they opened things up a bit last year, but nobody noticed.
Usefully, there is a QNX Board Support Package for the Raspberry PI, so you can target that.
QNX would be good for IOT things on Raspberry PI machines, where you don't want the bloat and attack surface of a full Linux installation.
> They lost their developer base. Support of open source tools on QNX stopped.
Right. These days it's better to invest into Redox OS[1] as a potential substitute for it (if work on real time capability). And with real time patches merged into Linux mainline[2] QNX doesn't stand much chance today too.
There is also a FWWM[1] "skin" that doesn't require long time abandoned C code - NsCDE[2]. It still requires X server (just like CDE itself) which becomes rarity these days. They need to port it to Wayland eventually.
It’s really sad it wasn’t open sourced. In the early 2000s I was triple booting Windows 98, BeOS, and QNX. BeOS was my favorite, but QNX Neutrino was great as well.
As someone who still uses a QNX phone, the Blackberry Q10 as my second phone, I’m not just optimistic for the return of the cross-platform and secure os, I’m rooting for it.
Especially for portable Linux handhelds.
If Blackberry were to release a phone tomorrow, it would instantly be the most secure android phone. I still run some of my favourite android apps on my BB10os via the android translation layer.
Some comments mentioning QNX can run Swift code makes me think of it could also run iPhone apps.
While Blackberry exited the phone market, I’m surprised to know QNX is still the most popular os for cars. With 275 million devices running it atm.
Swift != SwiftUI. You need the latter to run modern iOS apps written in Swift.
It's great that Apple are pushing Swift out there a bit, but honestly if they want the World to catch fire with it, they need to give away the Crown Jewels and get SwiftUI out there as well.
Meanwhile, it's great that QNX is supporting modern languages. I can imagine having a bit of fun with this developer desktop and seeing how modern tooling plays nicely with it.
> QNX can run Swift code makes me think of it could also run iPhone apps.
Not at all. That is like saying because it can run C, it can run windows apps. To run iPhone apps you would need all the libraries and runtimes ported, including the whole GUI. Just not happening.
I've only ever used QNX in the form of Blackberry products (mostly the Playbook), so I am afraid I don't what the advantages of it would be compared to Linux or something.
I know it's a microkernel which is inherently cool to me, but I don't know what else it buys you.
Can anyone here give me a high-level overview of why QNX is cool?
Hard real time (so latency guarantees), microkernel (and they actually mean it, so your device drivers can't hose your system), standardized networked IPC including network transparency for all services, ISRs at the application level.
QNX is hard realtime. At one point, its kernel had O(1) guarantees for message passing and process switching. It could have been rewritten without any loops. I'm not sure if that's still true.
It's also really compact. This used to be a great selling point for underpowered car infotainment systems. Some cars had around 1Mb of RAM for their infotainment, yet they were able to run fairly complex media systems.
QNX is also used for non-UI components, just as a good realtime OS.
We'll see if it reaches bare metal some time, instead of relying on QEMU(on Ubuntu).
In theory I'd be tempted to try, in practice not, because of all the back and forth between changing owners in the past, and resulting policies regarding availability.
I'm also very well served by some 'gaming distro', where nothing ever stutters or lags, on almost obsolete hardware, mostly clocked down to 800Mhz, with uptimes of up to 150 days. More isn't really useful anyways, because of updates.
But hey, Wayland! On QNX! With XFCE on top of that! Who would have thought?
What about photonic Plasma instead of some Generic ToolKit?
> We'll see if it reaches bare metal some time, instead of relying on QEMU(on Ubuntu).
They do list "A native Desktop image on Raspberry Pi" under What's Next, so hopefully soon:)
> In theory I'd be tempted to try, in practice not, because of all the back and forth between changing owners in the past, and resulting policies regarding availability.
Yeah, that gives me pause too. There was some noise earlier about open sourcing it; I do wish they'd actually do that.
It’s also running virtualized in a lot of cars! Although I’ve seen more and more US car companies switching from QNX to Linux. Chinese car companies I’ve worked with all use Linux instead of QNX, so perhaps that is the future.
I always liked their original UI - Photon[1][2]. Very lightweight and fast. Also a distinct and consistent style. I understand why they dropped it in favor of Qt and later Web technologies, but it's still a big loss.
[1] https://www.qnx.com/developers/docs/6.5.0SP1.update/com.qnx....
[2] https://www.mikecramer.com/qnx/momentics_nc_docs/photon/prog...
Glad to see QNX still progressing. I worked there as an intern twice in Ottawa and they're pretty damn good. Great place to work imo. I met some of the kernel devs there. Had the priviledge of working with one and he taught and demoed some of the kernel features to me. They gave us interns a full summer course on kernels, C programming, OS and some hardware. Fun times.
Sometimes I wish I could do this for mid career sabbatical.
What compositor is being used?
Did I just wake up from a coma? QNX desktop? Wayland XFCE? What is going on here
Seems like QNX was hiding in plain sight as a car os and a mission critical os for other devices.
There are tons of proprietary RTOS/microkernel products on the market. It's not so much hiding as it is crowded-out.
And none of them can hold a candle to QnX. I've used a whole raft of them and QnX stands heads and shoulders above the competition. The consistency of the implementation is extremely impressive.
This is a major throwback to the QNX demo disk, which bundled a browser and desktop environment onto a single floppy disk!
It was mind blowing at the time because Linux required at least 4-5 floppies to set up a text-only base system while QNX ran live from just a single 1.44MB.
Photon microGUI was included in that, and it blew my mind that you could literally kill and restart Photon without disturbing any of the GUI apps that were still running.
They also mailed a manual along with the demo disk, and I was amazed that QNX had built-in network bonding, amongst lots of other neat features. At the the time I was using Slackware & the linux kernel version was still 1.x, I don't think bonding came to linux until 2.x?
When was that? You can still run from a single floppy https://github.com/Steve3184/floppinux and some form of that was available for ages.
Linux was like that in 1995 (Slackware 3.1 or so). I believe QNX live was introduced in 1997.
He meant with X & web browser and so on. The QNX disk had gui + browser and a few other gui apps.
No I meant the base system. A system with X would take at least 20 floppies or so with Slackware 3. The whole setup was 80 floppies in total.
I’m sure it’s better now, it wasn’t so when QNX had come out.
Bring back Photon. It was dang near perfect.
Photon was what I was hoping for before I clicked the link. One of my favourite GUIs, closely tied with CDE.
Photon or not, I hated the period where they sort of moved to canned BSP deployment only, where in 6.5 I could just develop on a live system. This is nice.
Me too, although it's been a long time since Photon.
"This environment runs as a virtual machine, using QEMU on Ubuntu. To try the image, you'll need: Ubuntu 22.04 or 24.04." So it doesn't boot on bare metal?
Maybe they're trying to get away from needing Windows. The previous recommended development environment was cross-compilation from Windows.
The big news here is that they have a reasonable non-commercial license again.[1] The trouble is, QNX did that twice before, then took it away.[2] Big mistake. They lost their developer base. Support of open source tools on QNX stopped. As I once told a QNX sales rep, "Stop worrying about being pirated and worry about being ignored". They'll need to commit contractually to not yanking the non-commercial license to get much interest.
QNX should be licensed like Unreal Engine. If you ship enough products using it, it gets noticed and they contact you about payments, and if you're not shipping much product, Unreal doesn't care. This has created a big pool of Unreal developers, which, in turn, induces game studios to use Unreal. Unreal's threshold is US$1 million in sales.
Apparently they opened things up a bit last year, but nobody noticed.
Usefully, there is a QNX Board Support Package for the Raspberry PI, so you can target that. QNX would be good for IOT things on Raspberry PI machines, where you don't want the bloat and attack surface of a full Linux installation.
[1] https://qnx.software/en/developers/get-started/getting-start...
[2] https://www.theregister.com/2024/11/11/qnx_8_freeware/
> QNX should be licensed like Unreal Engine.
That sounds quite a bit harder to enforce for an OS designed to run inside, often not internet-connected, devices.
> They lost their developer base. Support of open source tools on QNX stopped.
Right. These days it's better to invest into Redox OS[1] as a potential substitute for it (if work on real time capability). And with real time patches merged into Linux mainline[2] QNX doesn't stand much chance today too.
[1] https://doc.redox-os.org/book/microkernels.html
[2] https://arstechnica.com/gadgets/2024/09/real-time-linux-is-o...
> One of my favourite GUIs, closely tied with CDE.
In case you're not aware: CDE is still around, open source, and runs on modern unix-likes.
There is also a FWWM[1] "skin" that doesn't require long time abandoned C code - NsCDE[2]. It still requires X server (just like CDE itself) which becomes rarity these days. They need to port it to Wayland eventually.
[1] https://github.com/fvwmorg/fvwm3
[2] https://github.com/NsCDE/NsCDE
Eh, there's always https://gitlab.freedesktop.org/wayback/wayback for that.
It’s really sad it wasn’t open sourced. In the early 2000s I was triple booting Windows 98, BeOS, and QNX. BeOS was my favorite, but QNX Neutrino was great as well.
I feel like Charlie Brown running up to kick the football and having Lucy pull it away.
As someone who still uses a QNX phone, the Blackberry Q10 as my second phone, I’m not just optimistic for the return of the cross-platform and secure os, I’m rooting for it. Especially for portable Linux handhelds. If Blackberry were to release a phone tomorrow, it would instantly be the most secure android phone. I still run some of my favourite android apps on my BB10os via the android translation layer.
Some comments mentioning QNX can run Swift code makes me think of it could also run iPhone apps.
While Blackberry exited the phone market, I’m surprised to know QNX is still the most popular os for cars. With 275 million devices running it atm.
Swift != SwiftUI. You need the latter to run modern iOS apps written in Swift.
It's great that Apple are pushing Swift out there a bit, but honestly if they want the World to catch fire with it, they need to give away the Crown Jewels and get SwiftUI out there as well.
Meanwhile, it's great that QNX is supporting modern languages. I can imagine having a bit of fun with this developer desktop and seeing how modern tooling plays nicely with it.
> QNX can run Swift code makes me think of it could also run iPhone apps.
Not at all. That is like saying because it can run C, it can run windows apps. To run iPhone apps you would need all the libraries and runtimes ported, including the whole GUI. Just not happening.
QNX is owned by Blackberry?! Blackberry still exists?
$100M+ last quarter, split between QNX and endpoint device software, https://www.panabee.com/news/blackberry-earnings-q3-2025
275M cars with QNX, https://roboticsandautomationnews.com/2025/12/19/blackberry-...
AI/robotics, https://qnx.software/en/industries/robotics
Exactly. And there’s a huge community of the old Blackberry qnx device owners as well still trying to survive.
Oddly Swift appears to support QNX but there’s not much information about it.
https://github.com/swiftlang/swift-testing/issues/868
Does this mean QNX supports at least some of the Apple software?
Not at all. Swift is just a programming language.
Hard to say. May be related to CarPlay.
PREEMPT_RT, Toyota's IVI shell for flutter and the AGL efforts has made qnx compete again
Wow, this could be quite useful for poking at the head unit in my car. It's also running QNX.
I hope you don’t end up diagnosing issues on the highway.
I've only ever used QNX in the form of Blackberry products (mostly the Playbook), so I am afraid I don't what the advantages of it would be compared to Linux or something.
I know it's a microkernel which is inherently cool to me, but I don't know what else it buys you.
Can anyone here give me a high-level overview of why QNX is cool?
Hard real time (so latency guarantees), microkernel (and they actually mean it, so your device drivers can't hose your system), standardized networked IPC including network transparency for all services, ISRs at the application level.
QNX is hard realtime. At one point, its kernel had O(1) guarantees for message passing and process switching. It could have been rewritten without any loops. I'm not sure if that's still true.
It's also really compact. This used to be a great selling point for underpowered car infotainment systems. Some cars had around 1Mb of RAM for their infotainment, yet they were able to run fairly complex media systems.
QNX is also used for non-UI components, just as a good realtime OS.
Totally miss this.
We'll see if it reaches bare metal some time, instead of relying on QEMU(on Ubuntu).
In theory I'd be tempted to try, in practice not, because of all the back and forth between changing owners in the past, and resulting policies regarding availability.
I'm also very well served by some 'gaming distro', where nothing ever stutters or lags, on almost obsolete hardware, mostly clocked down to 800Mhz, with uptimes of up to 150 days. More isn't really useful anyways, because of updates.
But hey, Wayland! On QNX! With XFCE on top of that! Who would have thought?
What about photonic Plasma instead of some Generic ToolKit?
> We'll see if it reaches bare metal some time, instead of relying on QEMU(on Ubuntu).
They do list "A native Desktop image on Raspberry Pi" under What's Next, so hopefully soon:)
> In theory I'd be tempted to try, in practice not, because of all the back and forth between changing owners in the past, and resulting policies regarding availability.
Yeah, that gives me pause too. There was some noise earlier about open sourcing it; I do wish they'd actually do that.
QNX is running on bare metal in a lot of cars.
It’s also running virtualized in a lot of cars! Although I’ve seen more and more US car companies switching from QNX to Linux. Chinese car companies I’ve worked with all use Linux instead of QNX, so perhaps that is the future.
Linux now supports real time too, even mainline. And there are open source RTOSes for smaller chips and critical applications like FreeRTOS.
QnX is expensive for commercial use, that's most likely the driver for this.
Bare metal! So, if you just give it enough time, it will run on Rust?
Only if it's exposed to elements. Meanwhile Rust already works on QNX[1][2].
[1] https://www.qnx.com/developers/docs/8.0/com.qnx.doc.neutrino...
[2] https://doc.rust-lang.org/rustc/platform-support/nto-qnx.htm...
which 'gaming' distro is that out of curiousity?