QNX is not a GPOS, so you wouldn't. I mean you _could_, but the real benefit here is hidden within: with the toolchain now included in this image, folks working on QNX projects can now build them right on target. No more messy cross-compilation.
In some cases it could also be an Android guest running as a VM on the QNX Hypervisor, where there are multiple guests (QNX, Android, Linux) making use of the same HW.
There's been talk about this on Reddit too, where our chief architect of QNX 8 broke down the decision. He mentioned it was ultimately a tough decision, but that in the end the cons outweighed the pros.
We still do that! In fact, the _QNX From The Board Up_ series on the developer blog is a small rip from that training content, adapted by Mr Brown. I hope we'll get all of it out there for everyone to benefit from in 2026 :)
Hiya! The bulk of my colleagues and I are in Ottawa and Waterloo Ontario Canada. We're a division of BlackBerry Limited, and have been for about 15 years. QNX itself is about 45+ years old, having come out of an OS course at the University of Waterloo. I work with a lot of people who are celebrating 25-35 year anniversaries -- very much still a lot of the same engineering and product talent here through all of the transitions.
We're in 270+ million vehicles on the road today, 1 in 7 globally (and growing!) It's awesome going to shows and reminding people that every time they turn their key (okay, okay: _push the ON button_), there's a good chance they are booting up QNX under the hood!
Some of my colleagues and I visited the class with the UW CSC in the Spring.. They said something like half of the students drop out in the first week after learning how much work that class is going to be!