Linked by Thom Holwerda on Wed 29th Sep 2010 19:07 UTC, submitted by poundsmack
QNX When Research In Motion unveiled its BlackBerry Playbook tablet on Monday, including the new QNX-based operating system it runs, I already speculated that it would probably make its way onto RIM's smartphones as well. RIM has now confirmed this suspicion.
Thread beginning with comment 443187
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

.. The problem with these proprietary OS's is that they are created and managed in a closed environment with a "small" team... Still, I'd be careful about encouraging platforms that are developed in a closed development model.

Even though I have not developed for QNX, quoted parts of your post do not make much sense. The same argument can be used for a number of platforms (Windows, iOS to name but a few) and yet development is not suffering.

Reply Parent Score: 2

frank Member since:

Again, I differ to experience. It's different when you're the market leader and innovating at a breakneck pace, creating standards faster than developers can keep up and generating profits hand over fist. However, there will come a time when innovation on a platform slows and quality is measured by how well it supports new standards led by other (possibly competing) companies. The same is true if you're developing for a platform that chases the market leader. My experience tells me that QNX lacks this support. It chases 80% of functionality of competitors well, but the last 20% comes at a premium and... in the past... they didn't quite deliver... for me. YMMV.

Cloud applications have brought development to the server and as long as you have an up-to-date browser, you're somewhat supportable. Server-based solutions are *somewhat* platform agnostic.

Embedded development frequently turns this around. Your platform becomes more important. You'll want your applications to work with hardware, ie, inserting gps coordinates to a picture, or something to that effect. From a vendor's standpoint, it's a constant struggle to keep up with new drivers, honing apis and developer kits. It's not going to be easy for QNX, despite the fact that they have RIM numbers.

Reply Parent Score: 1

dagw Member since:

The difference is one of scale. With major platforms no matter what you're trying to do, chances are there are lots and lots of other people trying to do exactly the same thing. And if there is a serious bug, that makes doing that thing impossible there will be a lot more pressure to get it fixed or for someone to find a work around. Also since windows has been used for so many different things for so long, chances are someone has already run across your problem and found a solution.

With small platforms like QNX, chances are you will literally be the only one of their customers trying to do that thing. Thus there is no one you can ask for help and you are far to insignificant for QNX to spend any resources helping you.

Reply Parent Score: 3

aliquis Member since:

Developers haven't suffered from the closeness of iOS? Ok.

Reply Parent Score: 2