Oh the irony...

Or did you intentionally bork the <quotes> tag?

Ah...but the killer feature BlackBerry brought to QNX is BES (BlackBerry Enterprise Server) connectivity. BlackBerry was never a mobile handset company. They were always a mobile communications company that sold two way pagers / phones. You see, BlackBerry has an international network in place. It's no longer needed to support their phones so it is being re-purposed to allow encrypted communication between all those QNX devices out there and a companies BES. Each QNX device connected means a license and each BES means a service agreement. If you bother to look at everything QNX is already running (Cisco network equipment, industrial automation [SCADA] equipment, medical electronics, and over 50% of the automobiles made today) you might begin to understand just how well positioned BlackBerry is to take advantage of the IoT. Earlier this year BlackBerry invested heavily in NantHealth and today they announced the HBox gen 2. A health monitoring device that will send its data in real-time back to the doctor via a BES. That's a potentially huge market.

Actually oil companies have been exporting crude products abroad (They still can't legally export unrefined crude oil) for a few years now because they can make more selling them in other countries. In fact this past June some restrictions were lifted and they started exporting unrefined ultralight oil

Dear OEM X,
We are intrigued by your new technology Y. We have begun production of our own version we copied straight from your designs and need you to sign the attached licensing agreement giving us complete autonomy to use your patents as we see fit. We very much enjoy our relationship and would hate to see OEM X lose its ability to purchase our chips at base rate and be forced to seek them from 3rd party suppliers.

Sincerely, Intel

If you're that nostalgic you can still do it the old fashioned way.

You had the same electronics theory professor I did!

Let's see...

You are correct. However Apple developed the CarPlay spec with QNX's assistance. Basically Apple copied the MirrorLink API and made their own version but they had to make sure QNX had a CarPlay plugin since the majority of cars today run on QNX. So to dismiss the QNX base is to deny that without QNX's help CarPlay would still be a concept instead of a shipping product. While the phone is handling the interface QNX is still coordinating the connection. Ford is likely switching to QNX at least partly to get CarPlay into their cars.

You're confusing the kernel with the windows manager. QNX runs the car. It links the engine and transmission to the cabin A/C and anything electronic. Without QNX the car will have a hard time starting/running. The Auto maker works with QNX and other third parties to develop a proprietary UX which is why you never knew the Audi, Volvo, BMW, Chrysler, etc. you were driving was running QNX. Apple is partnered with QNX on CarPlay. So it makes sense that Ford wants the added compatibility QNX will bring.

Well that settles it then! QNX is total crap.
That's why over 50% of the cars rolling off the assembly line today come with it installed.

I prefer the philosophy of right tool for the job. And QNX for now is the best choice for auto makers. I use Linux where it makes sense and when AGL matures it might become the best tool for the job. But don't expect auto makers to jump on it if they can't control it.

The confusion stems from thinking of QNX as the radio (infotainment system) instead of the vehicle control system. Past generations of automobiles separated the two but on modern cars they are integrated. QNX is used to control the entire electronic system including all the sensors on the engine and transmission, the cruise control, the intrusion detection system, as well as the cabin A/C. They all work in concert. That is why Android auto and CarPlay both run atop of QNX. Something Apple and Google downplay. QNX is sold a la cart. OEM's can purchase just the kernel or a whole host of off the shelf plugins that provide a very robust drop in ecosystem. Ford's MySync system runs atop Windows CE (Windows Embedded Compact) and the complaints from customers was it was just too slow. After years of trying to get the responsiveness they wanted they have finally admitted Windows Embedded Compact just isn't the ideal platform for their cars.

I own a 2013 Ford and a 2014 Jeep. The U-Connect system is light years ahead of the Sync system but the Sync system's voice control works better IMO. I can attest to the unintuitive nature of the settings on the Sync system. Pairing your Bluetooth device is indeed a challenge.

I suspect a liquid future isn't too far off if the price of 3M Novec drops just a little bit more

The botnet architects are just honing their skills for next years Turing competition.

Obligatory HaHa