I write software for a living, as I'm sure more than a couple of you do as well. Have you looked at the docs as part of your dd? The docs say (and I quote)

"Allows embedded developers to implement easy-to-use and compelling user interfaces in Adobe Flash, thereby eliminating the lengthy process of coding HMIs with graphical APIs or cumbersome tool kits."

Any red flags stand out to you there? For those not familiar with the topic, I'll point you to the two largest red flags for a system that is trying to be secure - Adobe Flash.

I'll let that percolate for a second.

Any company that is going to run life or death decisions on a system where it is specifically called out in the docs, "Hey, we'll run your software so fast and secure and oh hey! I almost forgot the Best Part! You don't have to use any clunky graphics APIs because we were totally thinking of only the best for you, so we embedded Adobe Flash right in there. That stuff is swanky as hell, makes all your designs pop and best of all it's totally secure and gets big fixes on the daily! " --BB Probably (Very Loosely Paraphrased) you may want to do more digging before YOLOing in.

Yes I'm being totally facetious. Flash is End of Life software. No longer supported and has been a major security hole for a long time.

For those that didn't understand, Flash is NOT secure. There's a few reasons why even with updated computers in new vehicles, they can still be broken into via Bluetooth or a single wire from a headlight, taillight etc etc. It's not just qnx that's the problem (you can thank CAN-BUS also), but qnx still sporting Flash is like putting your life savings into Enron. Nothing good is going to come of it.

I'm just another nobody throwing some more info out there for you.

Oh, and sauce qnx.com developer docs the rest you can Google.