Sorry but only a few geeks care about QT, and other developers care about the ecosystem and go where the money is. I wrote some QT code about 10 years ago and it was good, but is it so great compared to iOS/ObjC, Android/Java and WinRT/C# that developers would just flock to it blindly? I seriously doubt it.

That being said, we already knew Nokia was going to dump it, they already sold off the commercial support and licensing division and made a shallow claim "we're going to continue contributing to Qt," which almost always should be read by adding "until..." at the end.

I'm happy to see Qt back in the hands of someone who cares about it. Personally, I'm not much interested in whether or not Nokia plays in the sandbox.

But Android? On devices with a completely different form factor, input schemes, and resource requirements? I don't think that is feasible, particularly from a user experience point of view.

And having ported a fairly successful iOS app to Symbian^3 (using mostly Qt Quick/QML), I would seriously contest the claim of 1) Qt working like a charm on Symbian and 2) how well Symbian works in general.

Rather, that to provide the best user experience on each different type of device (i.e. to follow platform conventions and paradigms and take advantage of unique device capabilities where present), it's best to use platform specific tools and design your application to be consistent with the expected user experience for that particular device.

I did not mean applications like yours and never implied it was a toy.

I care about QNX too, it's such a cool RTOS.

But what can it do for RIM that can't be done by Darwin, Linux kernel or the NT kernel? As I said, us geeks by our very nature get excited by the things that the users don't, unless they can see a difference in usage.

Also, the fact that it's POSIX compliant helps immensely when porting existing code.

Moreover, RIM is doubling-down on Qt. It's unclear what this move by Nokia does, but I think you'll see a lot of Qt developers being hired by RIM. Whether they'll pick up the project and run with it is another story.

(Not trying to be snarky, but I would indeed be concerned about RIM following the same path as Nokia, especially considering the massive job cuts they've recently announced.)

RIM may be on the decline right now with BBOS, but you simply need to look into the great work they're doing to seed the developer community with the support they need to create great apps for BlackBerry 10. I know the typical thing to spout is that RIM is dead, long live Android/iOS, but if you actually looked into it yourself, you would see that RIM is doing some really great things with BlackBerry 10. They're reaching out to FOSS communities, seeding actual hardware, and making their tools easier to use than ever.

But I know that many, maybe yourself included, will call me a fanboi, downvote me, and won't bother looking into it themselves. They'll continue spouting this nonsense about RIM's death, never changing their opinion, and taking Apple/Google's word for it. That's fine, continue being uninformed.

The rest of us developers with an open mind will happily pick up the slack on the sinking ship that is RIM. We might be wrong, and you might be right. But what happens when we're right? Where will you be?

That's great, but the health of a company and it's products depends on a bit more than their developer relations team. The engineers at HP/Palm were also doing great things with webOS before it got axed entirely.

> But I know that many, maybe yourself included, will call me a fanboi, downvote me, and won't bother looking into it themselves. They'll continue spouting this nonsense about RIM's death, never changing their opinion, and taking Apple/Google's word for it. That's fine, continue being uninformed.

I have no personal stake in the matter nor do I particularly care whether RIM survives or dies. I was only making the observation that if I was a Qt developer that just got laid off from Nokia, I would not want to take up a job at RIM for fear of the same situation repeating itself in 12-18 months. I mean, in the best case scenario it's a gamble that BB10 succeeds in the marketplace at all. If I had a family to support I would be looking to find a less risky proposition.

> The rest of us developers with an open mind will happily pick up the slack on the sinking ship that is RIM. We might be wrong, and you might be right. But what happens when we're right? Where will you be?

The same place I always was? RIM's success or failure is entirely irrelevant to me.