Nokia new strategic direction. What is the future for Qt?

Published Saturday February 12th, 2011
358 Comments on Nokia new strategic direction. What is the future for Qt?
Posted in Announcements, Roadmap | Tags: ,

Wow, what a day… Nokia outlined its new platform strategy for smartphones, with Windows Phones as it primary smartphone platform in a proposed partnership with Microsoft… and Microsoft’s tools would be used for Nokia Windows Phone application development … and guess what, it has raised a lot of questions in the Qt community.

So the question is, what is the future for Qt?

Qt will continue to play an important role in Nokia. Consider the following:

  • The retention of Nokia’s 200 million Symbian-users is vital and Nokia has targeted sales of 150 million more Symbian-devices in years to come.  To achieve that Nokia needs to continue the modernization of Symbian in Qt – to keep existing consumers engaged and to attract new customers, either upgrading from existing Symbian devices to Qt enabled devices or entirely new to Nokia.
  • Nokia also announced it will ship its first MeeGo-related device in 2011, which will rely on the Qt ecosystem – and then will continue with MeeGo as an open source project for future disruption.  Nokia can’t afford to be behind the next disruption again and Qt can play an important role in making sure it isn’t.
  • With Qt Quick and Qt SDK 1.1 releases in the coming months we are expecting the Qt developer community to continue to grow – adding to the 400.000 developers using Qt today. Qt is developed together with the community and we expect the pace of innovation to increase even further as the community grows.
  • We in Nokia are one of tens of thousands of companies in multiple industries actively using and contributing to Qt, making Qt relevant for both mobile, desktop and other embedded developers
  • Qt expansion: We have continued to hire Qt developers and we will continue to improve and expand Qt in the future. Qt is great at delivering innovation; we have been doing that for 15 years.  With the upcoming release of Qt Quick, we will reach out to new users and make it even easier to create great apps and UIs for many platforms including Symbian and MeeGo.
  • The new Qt SDK 1.1 technology preview. We now offer only one SDK for both desktop and mobile developers, which makes it easier to target more platforms by using just one SDK.
  • Qt everywhere. Qt continues to make vast inroads into especially low end Linux devices and distro’s.  Qt also continues to provide a platform for others to innovate and differentiate upon. For example Dreamworks switching all their internal animation tools to Qt and making cool movies like “MegaMind” and “How to Train Your Dragon”.

Qt is increasingly popular. During 2010, we had 1.5+ million downloads at qt.nokia.com (alone) – twice as much as during 2009  – and with the up-coming innovation and additional investments in Qt combined with the introduction of open governance, I believe Qt will be used more than ever before.

Daniel Kihlberg
Director Qt Ecosystem – Qt Sales, Marketing and Services

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Announcements, Roadmap | Tags: ,

358 comments

Anonymous Coward says:

Thanks. Please answer one more question as soon as you are able to: Will Qt be ported to Windows Phone? I’d assume it would be technically possible, but would you be allowed to do that business-wise …?

Keith Rusler says:

Well that’s good to see that Nokia didn’t throw Qt under the bus, but then again in a way did.

When will Qt take the major jump and develop Qt bindings for .NET officially since now that Nokia started their thing with Microsoft. I know WP7 it isn’t possible for Qt on it. But what about their next version, etc.

A lot of people are becoming more interested in .NET than C++. When will Nokia take Qt to that area and grab those developers while still having C++ bindings for C++ people?

IMHO, If Nokia doesn’t do that, it kills the opportunity to expand Qt more and more. Because I know a lot of .NET developers that would jump on Qt faster than anything if it was only available to them. Right now they are locked in to Windows pretty much since GTK isn’t really going anything that great.

Qt has been able to go far. But targeting .NET will take it even further.

Aron (Nokia) says:

Qt will not be ported to Windows Phone 7. One of the key benefits of joining an established ecosystem is that there is an established toolchain that everyone uses. All Windows Phone apps will run on all WP7 devices. Adding Qt to the mix would only cause fragmentation.

Unfortunate from a Qt perspective but wise from a developer ecosystem perspective.

ABBAPOH says:

The problem of Qt on mobile devices is that there’s no normal device with it. I WANT to write mobile apps for nokia phones. Damn, but i DON’T want to spend 500$ for useless symbian device just only to run my applications. And if there won’t be high-level device with Qt, you can’t get new developers.

Keith Rusler says:

I have to say, Nokia made a bad decision jumping to WP7 knowing that Qt wouldn’t be on it. Now that Nokia did this, they basically went from Qt “Code once, run everywhere” to “Code once, run nowhere”.

Sure MeeGo will be here, but it’s placed on the back end in the doghouse. At least with Android, there is already android-lighthouse running on it. Now us developers get hug out to dry. Nice to see that Nokia bought Qt for mobile development not just for LGPL.

Now I personally don’t see Qt being anything really other than for desktop, netbooks. Simply because Nokia wanted a locked down system ran by a bunch of corporate proprietary people that are only out for the money. While Qt developers are now wondering what the heck we are going to do.

We was expecting MeeGo to be throw on the phones and have multiple choices like Symbian, now limited to 1 single phone that when it is delivered, no one will use it because we simply see no real reason to use it. Because Nokia doesn’t seem to care about Qt anymore.

But this is just my personal opinion. Nokia should just drop Qt and make the “poison pill” go in to effect and have KDE take over since Nokia refuses to make Qt do what it was expect and be on phones. But now it’s not even worth that anymore, just back to the desktop Qt goes. Screw mobile devices now.

qtnext says:

so in short, for me, Nokia need Qt to the transition with Symbian before using WP7 without Qt…
So Nokia just need developers for the transition … But after that ??? Who will develop Symbian application for a mobile toolkit dead in the egg ?
I think we need something more reliable than that … Just for remenber :
– Elop has started discussion in November to switch to WP7 …
– At the same time, there was a lot a communicate that said that Qt is only way to develop for Nokia … far more communication than ever ….

Why trust Nokia now ? The only target for Nokia is clearly to use Qt (and community ) for the transition … Is now Qt profitable without the mobile target ?
So Qt Mobile is commited to death : Symbian for the transition, Meego as a hobby :), Android is the concurrent … so no android port, Ios the same …
And I don’t know why will Nokia invest in Desktop : they don’t use it on their Ovi Suite ( and clearly the before 11 Februar, the roadmap was clearly focus on Mobile dev)

we don’t want to be the turkeys of the party 🙁

Wafflbot says:

“All Windows Phone apps will run on all WP7 devices.”

All 3 of them!

QtDEv says:

FULLY Open Source Qt under the GPL if you plan to throw all us devs under the bus. We no longer trust you.

When Elop came in he said that Qt will be the main framework. Symbian and MeeGo would be unified through Qt. We all stopped working on Symbian C++ and started learning Qt. We have now wasted 6 motnhs of our family’s lives on a dead end. If I knew this was going to happen, I would have started learning Java instead!

Nobody will make apps for a dead platform! Don’t you get it!?!?!?! All those people who were bamboozled into buying Symbian^3 phones will have no app future. People expected an ecosystem to grow around Qt. By not allowing Qt on Windows Phone, you have killed all hope for them. Don’t give us the bull about fragmentation because there is no fragmentation with Qt. Qt already runs on WinCE. Microsoft just wants total control that’s why they don’t want Qt.

They did this out of spite to kill desktop Linux since Qt apps would also work on desktop Linux.

There was no “burning platform”. Qt was gaining momentum and was warming up the developer world with it’s cross-platform capabilities. Elop poured gasoline on the Qt platform and set it on fire. Elop is an arsonist or better yet, an economic hitman.

I already returned my brand new E7 that I paid 580 euro for after yesterday’s announcement. Don’t expect anyone to be dumb enough to buy any Symbian phones for the rest of this year.

Chris Browet says:

Could we have real comments from a real Qt guy, please?
Not PR junk reiterating Nokia BS…

We all understand Qt has no future at Nokia.
The honest thing to do would be to quickly sell Trolltech to someone really committed to it or give Trolltech its freedom again.

Otherwise, the foreseeable outcome will be Qt guys leaving the sinking ship and leaving back an empty shell…

Bilahs says:

QT,Nokia and Symbian are going spirally down, QT developers stick to you slimy toolkit and see ya after 2-3 years , after exploring all platforms i’d prefer sticking to .NET and Cocoa, Rest all is BullX

dotpeople says:

When will more detail be available (as announced on Friday) about possible Qt support for native (non-Java) applications on Series 40 mobile phones? Targeting the “next billion users” at the low-end does have strategic value for cloud service developers, but these new users won’t be purchasing on-device apps.

What is the 2011 time frame for Qt Quick and Qt SDK 1.1 final release, with corresponding Ovi store and firmware updates for Qt Quick support on Symbian^1 and Symbian^3 phones?

> We in Nokia are one of tens of thousands of companies in multiple
> industries actively using and contributing to Qt, making Qt relevant
> for both mobile, desktop and other embedded developers
..
> with the up-coming innovation and additional investments in Qt
> combined with the introduction of open governance, I believe Qt
> will be used more than ever before.

Is Nokia now open to supporting Qt and Qt Mobility ports (done by “companies in multiple industries”) to WebOS and Android? Developers must now provide immediate business justification to their finance departments and investors, for further investment in Qt apps on Symbian.

If app development for Qt Mobility on Symbian phones can be amortized over a sizable future footprint of non-Symbian devices, then Symbian developers can obtain finance approval for Qt apps today.

It is not financially relevant whether the sizable base of future post-Symbian devices could be constituted of Meego, Android, WebOS or WP specifically. Only that the post-Symbian devices could be (or already have been) purchased in large quantities by consumers on platforms with commercially viable app distribution channels.

Aron (Nokia) says:

Wafflbot: I am pretty sure Nokia will help boost the numbers of WP phones on the market…

QtDEv: I understand how you feel, I really do. I also hear your frustration regarding Symbian. Keep in mind though that there will be at least 150 million Symbian devices shipped over the next couple years, which is a not-insignificant installed base to target from an app dev perspective.

Another point is that Qt is already licensed under the LGPL.

Look, I started with Trolltech 11 years ago so I have rather strong feelings regarding Qts future as well. This is not the end of Qt, just a bump in the road.

David says:

Nobody will develop for a dead platform. Namely Symbian, Meego or Qt (except for desktop).
There is no trust on the company either.
Should I risk to learn WP7 knowing that Nokia may change their mind AGAIN? No way.

Moreover users that buy a new phone will find that their paid apps no longer work on their new device.
This is corporate suicide.

Jeff Taylor says:

Well of course Symbian will sell phones hopefully. But then what when it hits the end of the road? There is no Qt for WP7. What other point of Qt other than the desktop?

MeeGo won’t hardly be adopted. If it does, probably be killed off also. What’s stopping Nokia from doing that right now? They are all behind the retarded WP7 rush. Now if only Nokia would get off their arses and make Qt for WP7. We probably wouldn’t be all worried about Qt’s future.

Well, considering Qt on mobile is going to 0, is Qt on desktop getting enough incomes to justify (for nokia) its survival

Aron (Nokia) says:

Chris Browet: I hope I qualify as a “real Qt guy” (started in TT in July 2000). Qt does have a future at Nokia. That is why we continue to fund development and hire new people.

Don says:

Elop is the 7th largest individual microsoft shareholder (according to Finnish newspaper today)

Seriously, they announced EOL for Symbian, who is going to start development now? Those 150M new sales (dreaming imho) are just there to be switched to WP7, Nokias position is very clear, they are not a partner, but a Microsoft division now. Qt stands for cross platform, you’re a means to an end to convert Symbian users to WP7 but they’d like nothing more than for Qt to go away.

The whole show with Balmer and the vomit worthy “Steve and Stephen” was a disgrace. I’d like to be optimistic, but I remember the “Qt all the way” chanting not too long ago all too well.

I am so sorry for what is happening. Qt is such an awesome codebase and its people are the best.

Alesete says:

Fragmentation? Qt can looks like the platform where the app is running!
With lighthouse Nokia had the great opportunity to bring Qt to Windows Phone 7, Android, symbian, meego and any platform nokia would wants to adopt, and have the same applications, SAME MARKET! on them…. that’s the perfect ecosystem and the platform where all developers want to build their applications (key point of this game).

Sorry, but with no Qt port, Nokia did the worse strategic movement of its history… Great Microsoft’s trojan you get with elop…..

P.et says:

Qt now is just a waste of time and space.
Go to Google and do something really useful.

Chris Browet says:

@Aron: Yes, you do 😉

But seriously, what “future at Nokia” do you see? I’d like nothing more than a bit of optimism…
The “150 mo symbian device” is hardly a future to me, and the fact that you are still hiring might only be a sign of Nokia confusion…

Claudio Beatrice says:

There’s just no way developers will still put their trust in nokia, that’s the point. As many people said, Qt was gaining _real_ momentum around nokia’s plans for the future, with symbian slowly shifting on the mid-low end of the market and MeeGo getting the upper class. Projects like lighthouse were freaking promising as well, because they made people hope to have a unique and amazing platform to develop for and ship everywhere. When this dream started to take a shape, with first applications running on real devices, it was just all screwed up. Saying that nokia will support Qt is just called ‘hypocrisy’. Nobody wants to develop for a DEAD platform now that there’s no more plan for a tight integration between it and the future(MeeGo). So please stop fooling people because nobody believes you anymore.
I really hope that somebody will take care of Qt seriously, Intel perhaps, I don’t mind.
I’m disgusted.

Philip says:

Nokia must give the Qt brand to the community and establish a Qt Foundation that can maintain and develop independently the framework. Just so KDE will live, will be made the port to iOS and Android and someone else will invest in Qt. LibreQt, today, forever. Please nokia, do it now!

Keith Rusler says:

Well, considering Qt on mobile is going to 0, is Qt on desktop getting enough incomes to justify (for nokia) its survival? 🙂

Ben Lau Ben Lau says:

Fragmentation?

I wonder now it is Nokia , or Microsoft Nokia. Why Nokia need to consider the problem of fragmentation of window phone??

Nokia do not hold , lead , the developer community of windows phone. It is belonged to Microsoft! Nokia is just one of the provider of the window phone. It just like HTC. Where you see HTC developer group? Except those who are hacking HTC product for other purpose.

Qt is the way , and the key , to gain the control of the development and hold your own developer community. Otherwise, Nokia will be downgraded to a OEM company only. Nokia will have no chance to have his own OS.

But if you have Qt, when you finished the “next generation OS”. You may call those who is developing Qt applications back to your system.

Kensai says:

Come on, guys, give it a break.

Nokia’s strategic direction might have indeed changed, but this is only true for the mobile segment. There are lots of other devices (tablets, PCs, etc) that Qt is and will still be hugely relevant. Once you learn the Qt toolkit there is really no way your skills can’t be used somewhere.

And nobody has said that in the future Nokia won’t be selling enough smartphones to amend the deal with Microsoft for a WP7 port of Qt.

Time will tell, enough already with all those bitter comments.

This is bull c**p.
Nokia showed how stupid the decisions about Symbian + MeeGo co-existence were, and now they want to add more problems with a new WP7 based environment.

Just because you have multiple departments, doesn’t mean you can handle so many, so different environments.

Qt+Symbian+MeeGo is now a dead path. No developers can feel confident (and intelligent at the same time) at sticking with this path. No matter how much Nokia says that they should.

How can ANYONE trust Nokia’s word now, after having kept changing direction in past 2/3 years? Qt was, technologically wise, a great direction. But the execution, the gap between good code and a phone was never really closed (please, stop saying that N900 is a device that can barely compete with real smartphones like Android based or iPhone).

And now? Now M$ will take it’s space into Nokia devices, leaving the “lower hand of the latter” to Symbian. For which no developer (a part from Contracting-Out companies) will give any attention.

The only platforms that matters for developers are the high-end ones. Where people buy costy phones and use it on a daily basis, installing all sort of useless (and useful) apps. The low-end is just for phone calls, sms and facebook. And there no developer that matters will spend time using Qt.

Either Qt is ported to WP7, or it’s better if Trolltech is sold out and goes back to what it was before the Nokia-shit-storm.

Nokia let everyone down. Full stop.

Philippe says:

Thanks for the news, which I consider good.
As you say, Qt is great at delivering innovation. And after all, maybe (after) tomorrow Meego is preferred by phone users.
“Nokia connecting people”… then that means Nokia must maintain “universal” tools in his bags… sounds like “Qt (almost) everywhere”.

Albert Astals Cid says:

If Nokia really wants to push Qt on Symbian may I ask why they release new phones like the C5-03 (we’ll let naming discussion for a different day) that are perfectly capable of running Qt but do not have Qt installed?

GeceBekcisi says:

So in summary, great projects and higher profit margins are exchanged for couple of millions M$ offered for the short term. Once a giant Nokia, became the tiny bitch of M$ under Elop’s pimping. OPK should never leave but a bunch of idiotic shareholders couldn’t get his long term vision, what a pity.

Good-bye Nokia, now I have to find another company that’ll offer what I need, you’re not it anymore.

Miguel (ON) says:

I really really hope these words not to be empty.

:o)

Chris Browet says:

@Kensai: You are perfectly right. There are huge opportunities for Qt everywhere!

Just not at Nokia, IMHO, and we don’t want N$ to let Qt die out…

Chris says:

All the best to Qt, whatever the future holds.

I’m just an enthusiast and a Nokia N900 lover, but I feel that Qt’s time at Nokia is slowly coming to a close, just as Symbian is. Neither are dead, but as Rafe from AAS put it there’s now a “timeline” for its demise.

What sorrows me most, is that Qt will not reach the limelight it was meant for and deserves. Being stuck on a platform slowly sinking to the sea (not referring to anything here) is no place for something as exciting as Qt. Your efforts mean the world to everyone and everything related to MeeGo, in addition to a number of other platforms.

So the best of luck to everyone at TT and I really look forward to seeing your handywork in exciting new products!

Have a great year 2011!

ex-developer says:

Why would any company want to buy software that runs on Symbian if after 2 years they can no longer buy new Symbian phones? Do you think they are going to buy used ones from Ebay one by one for hundreds or thousands of people? Hah. Dream on. Android, here we come.

jonnyjl says:

Everyone, read between the marketing speak and spin.

They’re going to drain their current consumers with more unrealized promises, but this time around they’re not even going to try, they’re just outright lie and keep stringing us along, hoping we’ll support them financially during this transition to a crappy, closed ecosystem.

Dump your support now.

I don’t know why Nokia employees are even trying to defend this move, I guess they think they won’t be on the chopping block… Well not yet.

They continue to hire Qt developers after the good ones are leaving because they see the writing on the wall.

Fantomas2006 says:

In a few months, with quarter result lower than expected, I bet you 10 € that the MeeGo-related device will be canceled… I think this device is a delusion.

Vesa says:

What about “Code Less, Create More, Deploy Everywhere”? Nokia just made that a bull*hit statement, am I correct? It wouldn’t be fragmentation to be able to code with Qt for the WP7 phones, it would be the best f*****g thing ever!

An insider says:

Nokia has taken way too long to realise the potential of Qt to create the device-side components of the “third ecosystem” to rival Google and Apple.

Nokia wasted millions on internal engineering effort on a Symbian^4 UI by Nokia engineers based on Qt (effectively proposing to fragment Qt) while the Qt software engineers were off developing the “rival” cross-platform QML. Result? Symbian^4 canned at the 11th hour and QtQuick & QML not ready for serious productive use yet: don’t think so? – no real UI components – just UI primitives, so you have to reinvent almost everything for every app. EVERYBODY should have been pulling in the same direction for the new UI, but internal politics has shafted both projects. Qt software organisation’s arrogance and dislike for Nokia was part of the problem too – Qt software was left to do their own thing for far too long when they should have been given the leading role in creating the new Nokia user experience for Symbian and Meego devices. Now it is too late. Both Nokia and Qt software have failed to execute on what could have been a killer strategy.

M$ will want to kill Qt – no doubt about it. On mobile it is dead, whatever you claim about another 150 million devices. Last October’s ecosystem statement from Elop was all Qt, Qt, Qt. It is now dead as part of Nokia’s medium and long term strategy. We don’t believe what Nokia says anymore. M$ will try to kill Qt on the desktop too if they get the chance. Cross-platform? Write once, compile anywhere? M$ are monopolists, the last thing they want is a cross-platform solution.

Nokia will ultimately be absorbed at huge discount by Microsoft as its hardware production arm (probably towards the end of 2011 by which time the market share and profits of Nokia will be in terminal decline).

Good luck Qt software. Don’t let M$ strangle the best cross-platform framework for desktop development. You need to figure out how to avoid being quietly strangled by Microsoft.

Aamir Maniar says:

As a developer in Microsoft Technology I had always wished to have window mobile in nokia phones. But nokia had leaned towards java rather then windows. These days I started developing using Qt, nokia started liking Microsoft. It’s surprising…

http://www.technobits.net – Always remain technically updated

P@ says:

As a N900 owner, I can tell you how much Nokia is good in innovations but does not promote and develop them enough.
Qt is full of promise (as was Maemo) but will probably become a dead-end, a niche in respect to smartphones.
Qt will of course not disappear because it is used a lot but the big hope of Qt becoming a cross-plateform tool joining even desktop and mobile world seem to have gone a bit more far away. It will probably not disappear as will Symbian, because Nokia just cannot 😉 !?

Bee says:

So,will Qt remain cross platform for C++ Applications,or not?
Thank you.

BogDan Vatra says:

Trolls, what is wrong with you? Have all gone crazy ?

About what ecosystem do you bullshit us? Do you know that Microsoft not only gave WP7 for free to OEMs, but they even “sponsored” the hardware to be cheaper than Android phones? Do you know that after OEMs shipped their first devices, after they seen how crappy is it, some of they canceled any other future projects with Windows Phone 7?

Do you think you’ll (Nokia) make cheaper smart phones than Chinese OEMs ? Do you think WP7 is better than MeeGO, Android or iOS? MeeGO was your ONLY chance to be No.1 again, it was your ONLY chance to be YOU and to be different. Do you think people buy Apple phones because they are cheap?

After Elot Savior make the big announce, your Nokia stocks drop with more than 13% ( http://www.google.com/finance?client=ob&q=NYSE:NOK ) , god, all of you are blind? Don’t you see you are going down ? Did, Elop Savior, fool you all ?
Wake up guys !

I’m not worry about Qt,(being licensed under (L)GPL so is safe, when Nokia will stop the support (or even sooner), the community will fork it), I’m worry about Nokia, actually now I’m disgusted about it!

Javi Moya says:

QT Desktop is dead since Nokia adquisition.
And now QT Mobile is dead too. (who is going to learn and develop to a deprecated low-end platform??)

And there is no a powerfull community to support alone QT.
QT needs talented Trolltech guys.
And these people is going to work now with WP7.

🙁

Nic says:

And here I thought Nokia had a very smart plan up its sleeve: having lost the smartphone OS battle, they’d render the OS question moot, and create a huge developer ecosystem in the process, with “Qt everywhere”. Boy do I feel stupid having fallen for that!

I’ve just spent 4 months learning Qt and coding the apps that form the core of my start-up business with it. Desktop release for now, but the plan was to release on multiple mobile platforms within a year, as MeeGo, Android-lighthouse, WP7-lighthouse, etc. came online. Oh yeah, and perhaps a Symbian port in case those phones ever developed any kind of sexiness.

I really feel kicked in the nuts by Elop. The only thing that could make me stay with Qt for mobile development now is a firm commitment to release Android-lighthouse, as soon as possible, with real resources behind it. C’mon, I need at least one popular platform that I know my code will run on, and sorry but neither Symbian nor MeeGo qualify.

Too bad – an OS-agnostic Nokia might within a few years have dominated mobile development through “Qt everywhere”, even shackled to Microsoft. But by agreeing to lock Qt out from its own future products, Elop has shot Nokia not just in the foot but right through the brain.

GOro says:

The problem about that; nobody wants Symbian anymore…

Enzam says:

To Aron & other devs who are really committed to Qt, please don’t believe in the stupid promises the company is giving you now 😛 or if you do know that Qt has no future in Nokia don’t try to fool us with bullshits.
I hope some company like Canonical Ltd. will come to rescue.

oiaohm says:

No matter how you put it QT has been backstab by Nokia.

All you have todo is look over to mono lead developer he is celebrating. To develop on all mobile phones now you can use Mono or MS.net. Sorry Nokia are made QT dead in the water for mobile development.

Of course MS does not want WP7 platform fragmented because then they will have to fight.

Unless of course WP7 keeps up its on going rate of failure to sell. Either way Nokia suffers. QT undermined as a cross development platform to the advantage of .net. Great move leading to Nokia no longer supporting QT. Or stacks of phones produced with MS logos on them that can not be rebaged and cannot sell.

ManoMan says:

We want Qt be ported to Windows Phone even if that’s against Microsoft’s will (Xbox 360 would be nice too).

Also add Qt for iPhone and Android please, because “Qt everywhere” means everywhere.

Philip says:

Intel market cap (NASDAQ:INTC) = 121.38B
Nokia market cap (NYSE:NOK) = 35.05B

Nokia: sell the Qt division to Intel and you will save your face…
Intel: bought the Qt division from Nokia and you will conquer the world !

Meego + Android + iOS + Win + OS X + Linux all in Qt for ultra speed productivity.
Qt Creator + Intel Compilers for ultra speed performance.

Intel come on !!!

Chakie says:

Well, I for one will now significantly reduce my time investments in Qt and focus on iOS and possibly Android instead. I see no future for Qt, and I have been using Qt since version 0.95 (or so). This was the most stupid decision Nokia could have ever done, but I can’t say it wasn’t expected…

Anonymous Coward says:

When a company says a successful product continues as opensource project supported by the community, it really means they are killing the product.

You just have not realized it yet.

qtnext says:

Go here … it’s exactly what I am afraid :
it seems that Nokia is not the first shoot of Elop …. seems Director also

http://piacentini.blog.br/2011/02/elop-is-after-me/

et3rnal says:

FINALLY a good news 4m Nokia 😀

im sure if Symbian team doing a great job in their next update n the new phones got many ppl Nokia wont kill the system,

Nokia already need at lest till the end of the year to get their first WP device n thats the only time 4 symbian to prove itself again 🙂

im sure symbian with QtQML have a great chance but yesterday news killed many developers dreams n took them away 4m Qt n Symbina ;(

plz plz plz encourage developers again n fix the seen 😐

Kurt says:

Everyone who gets in bed with Microsoft gets backstabbed at some point but getting a Microsoft manager to run Nokia’s business was retarded in the first place.
Those always act as mole in favor of Microsoft.

When Microsoft releases its own phone, you’ll get f*cked in the ass just as all PlaysForSure partners who got screwed over via Zune or all Windows game developers who got screwed by MS’ Xbox focus or your MeeGo partner Intel who invested in Linux after MS screwed them twice! First dropping Itanium support, later refusing to properly support Atom.
Don’t you talk to your MeeGo partner to learn from him?!?!?!

I can’t speak for everyone else, but you lost at least one loyal Nokia customer. I’m probably going with HTC and Android for my next phone…

Thierry says:

I’m a troll (in dev since 2006) and yes there is some level of uncertainty aroundt’s future. Yes we believed that all Nokia phones and more wouldbe powered by Qt somehow. This is not going to happen, not short-term at least.

It is a sad realization for all of us developing Qt. But we stay 100% committed to Qt. It runs on many other devices than phones (including desktop). We’ll keep developing Qt qnd making it the best developer experience available.

Javi: no, we won’t work on WP7.

OpenSourcenist says:

@Aron Do you really really believe that:
– nokia will ship 150m symbian devices and not cancel them?
– someone in nokia is really doing their work trying to ship symbian phones instead of spending their time finding new job?
– someone is really going to buy those phones?
– someone is developing software for them anymore?
If yes, then you probably believe santa claus also 😀

Brian says:

I don’t think anyone has WP7 support on there roadmap.

Tsiolkovsky says:

This post exactly describes my concernes: http://piacentini.blog.br/2011/02/elop-is-after-me/

I think the best to go forward is to separate Qt from the bad company Nokia has now become and in this way save Qt from Elop assasin (economic hitman).

Dear Qt enthusiasts,

I thought I would drop a few thoughts about Qt. Considering the climate, now is the best moment to do it.

I’m a young developer. I spent 8 years coding in C++ and 6 using Qt.

The Qt framework is hands down the best framework I’ve ever used.

So what’s so special about it ?

1. It’s developed by super talented people: Kent Hansen, Thiago Macieira, GUNNAR, Henrik Hartz and a lot more. They’re not just great engineers they’re also listening a lot.
2. The framework itself is the best product for multiplatform PC development.
3. It has the best community I have ever seen.

Take a look at http://www.qtcentre.org, It’s not even an official Qt website but it’s one of the most supportive service one can use.

You’ve been using Qt recently and you love it ? Now is the right time to show support and love. We are stronger than marketing choices. If you decide to support the Qt Framework it will continue to improve and surprise us.

Beside, I don’t know about you but I don’t see myself using any other framework for the next decade.

So let’s trust and support the Qt team. This is not a failure, it’s an opportunity to bring beauty from pain.

I believe in Qt Software, so should you.

Benjamin Arnaud.

jmk says:

Sounds like Qt is now officially rescue breathing machine for Symbian. Lovely.

Ann Onymous says:

You know what the funny thing is. Microsoft and Elop must already be prepared to defend themselves in the court. They kill Nokia and Qt and they are like, “so what ? sue me!”.

kale22 says:

fork?

Raine says:

Just what happen yesterday? In reality nothing! We are still protected by lgpl and free qt foundation. Just don’t do anything haste. Let’s do what’s best.

Jason says:

Those of using QT outside of mobile applications desperately to be re-assured — in a very concrete way — that we’re not now developing on a dead platform. Please! I’ve made a 2 year investment in learning QT for desktop development. However, I’ll have to abandon it if it looks like Nokia is going to kill it off. And no, I’m NOT AT ALL re-assured by those who say it can always be “turned over to the community” . QT MUST a core, full time, PAID team to keep it competitive for commercial applications.

marshall says:

People can say whatever they want about forks and all the usual wishful thinking that is brought up on these occasions. Qt is what it is because it had the backing of a company that cared about it and pumped millions into it. Without that, it may continue but it’ll stagnate and become less and less relevant.

I hope some company with the interest and resources steps up and just takes care of Qt. It’s too good to let it go to waste.

Stephen Chu says:

The switch is a done deal. Bitching, swearing, and calling Nokia and its employees names won’t change it. And remember it’s a decision must be made by Nokia. The company is on life support. Continuing the current path is certain death. They have to change. And I don’t see any of the options they have is going to leave Qt intact. Whether it’s a right decision, we can all disagree. But leave it to the market to decide.

Also please remember the majority of the Qt functions and its clients are DESKTOP applications. Qt has live by providing desktop solutions for a long time and there’s no reason it can’t continue doing that.

Now for Qt to become a valid mobile toolchain, the only option left is to get Android port ASAP. MeeGo may be great. But it’s in no better position than Sybiam right now. And that is not very good. However, the partnership with MS may get in the way of Android port for sure.

I wish all Trolls and Nokia people luck. This is people’s livelihood we are talking about. You brought a great C++ framework to the world that makes my job possible. Thank you. And let’s work together to keep it working.

Jason says:

Everyone, stop talking about forking!! Be realistic, look at the number of commits from Nokia versus everyone else combined. NOTHING is going to replace the hundreds of thousands of man hours a paid, full-time team can afford to put in. If you think so, then simple question: are YOU planning to hack QT for 40 hours a week? If Nokia ditches the Trolls and it’s not picked up by anyone else (Intel, are you listening?), it is OVER outside of KDE. You’d be crazy to develop on a practically stationary platform when WPF, Cocoa, etc. keep moving fast ahead.

I dunno, I asked the same question Albert Cid did; and what would stop Nokia from later dumping Qt out like it did for mobile. Not much I would bet.

Besides, we know that “Keeping existing customers” just doesn’t exist in the mobile market. pff. snarl.

Stephen Chu says:

One thing people keep forgetting is TrollTech was a company by itself before Nokia bought it. It was living by itself and doing OK. There’s no reason they can’t go back to do the same.

I actually prefer that way since they will be free to port to whatever platform they see fit and don’t have to be restricted by marketing policy from higher up. can we say, Android? 🙂

DAXaholic says:

That are really bad news, but i think this won’t be the end of Qt (and MeeGo); it’s used by so many developers and companies. I believe that a lot of companies would adopt it with the greatest pleasure. MeeGo also has a strong backing with Intel. So perhaps Intel is such a company which would like to adopt Qt ?! 😉
Anyway, I’ll continue using Qt for my future development!

Rovshan says:

I used C# and .NET for more than 9 years to develop quite serious things and 5 months ago I switched to using C++ and Qt. My opinion is: Qt is much much better. I’m planning to stick with it and I’m sure that such a great piece of software will not die.

bhairav says:

Was a QT Developer But now Changed It’s a pity that the Qt Eco System had to take beating form Microsoft .net platform as CEO Steve ballmer knew people would stop targeting Qt with an announcement like this don’t give us
crap,WE Know (or pretty much Guess whats going on inside the company),Must be good day for Microsoft Killing 2 birds with one stone!!!(One Gets their Windows to a new Level Which they think it would!!!!,the other kill a Developer framework before it kills them;Typical MS Strategy), However just one thing now developer community is going to abandon QT and .NET and maybe we will goto GTK+ or Android

Rodrigo says:

I guess the developers opinion is very clear here and that could be easily predicted. If anyway such thing was said is becouse Elop’s words are completely empty about MeeGo and Qt. And without Meego and Qt Nokia’s future will be for ever atached to Microsoft. My question here is why you Daniel Kihlberg has not joined your cooworkers on protesting against it and if you think we are stupid to believe what you just said on this article?

Thanks

An insider says:

Qt could go back to being developed by a separate business entity like Trolltech, and that could work again, as their previous licensing model proved.

But however you look at that, it drastically reduced the scope of what Qt could have been. Even if Intel picks it up and runs with it as the application development layer on top of Meego, do Intel have the power and reach to make it a serious contender against Apple and Google devices, frameworks and services? I doubt it.

The best you can expect is that Qt goes back to being what it was – an independent company supported by framework licensing and the best way of doing cross-platform desktop development. Nothing wrong with that, but much less than the vision that was promised by Nokia.

IMHO Nokia should not have got into bed with MS at all (who are not offering WinPhone exclusivity it seems). A WinPhone strategy is just as risky, possibly more risky that aggressively pushing a Mobile Linux (Meego) + Qt Quick solution. It certainly does not immediately crack the US market share. No Nokia Winphone devices until 2012 it seems. It’s not like Nokia have chosen a partner with a lot of success with mobile OS! The problem is that Nokia and Intel have failed to get Meego to market and the Qt Quick solution is immature (compare it to Android and iOS widgets).

Nokia should have extremely aggressively pursued their Qt strategy – effectively wrapping a solid Symbian core with new Qt UI and Qt Mobile frameworks for a completely new user experience. Symbian is only hated because of the old S60 Avkon UI, which is what Qt was supposed to fix. Apps and services could then have ported easily to Meego platform, thanks to Qt. Going with Microsoft and abandoning Qt is a massive gamble and one that will ultimately reduce Nokia to a simple mee-too hardware manufacturer.

Google have the most to gain from this massive mistake.

Aron (Nokia) says:

Listen, I hear your frustration and I can only say I sympathize with you all. Friday was not the best Qt-related news I have ever received…

I don’t have all the answers but I can tell you this: We are still going to continue to develop Qt. That is a fact. We are going to push Qt, we are going to embrace our new challenge regarding being a “disruptive technology”.

We have a tradeshow booth at Mobile World Congress next week in Barcelona. Anyone who wants to chat more come on by. For those not there we will try to keep updating you via this blog and other channels.

Sergey B. says:

I hope this barrier save Qt, may be not in mobile market, but in crossplatform desktop space.
http://qt.nokia.com/about
We are owned by Nokia and Qt will be used extensively in Nokia devices, but we operate within an information barrier that lets us work independently with companies external to Nokia including those in Nokia’s competitive space.

qtnext says:

If Google wants more apps …. He just has to help to the LGPL port of Qt to android … I think now a lot of developer will be happy to develop for android with Qt ….

Ben Lau Ben Lau says:

Hi Aron,

Developers and fans like me are shocked by the news , and worry about the status. Because it is really an excellent framework and we love it.

It is great to hear that you and Nokia will still going to develop Qt.

I know that it is a hard time for all Nokia employees. I wish you all the best.

Yuvraaj Kelkar says:

Qt is the only way for Nokia to dominate over the dumbphone and smartphone market. Therefore I humbly request you to port Qt to WP7.

Think about it: If Qt is ported to WP7 (or a subsequent Windows phone) the entire Feb 11th PR nightmare will be forgotten as developers around the world rejoice and get back to backing Nokia.

An insider says:

Aron – I think you are a little bit in denial.

Last October the Nokia management team stated that the developer ecosystem was Qt – hence the new Qt SDK which allows developers to build QML/Qt apps for Symbian, Meego and desktop.

Now management state that the future is Windows Phone 7 without Qt. Symbian is a “franchise platform” (milk the last value out of it for next 150 million devices, then can it) and Meego is a project for “disruption” (no actual serious commercial products, except possibly one later this year for geeks).

Crucially Qt is only for the dying platforms – Symbian and Meego that are not part of the long-term strategy. This is public knowledge. Nokia intends to use Qt to somehow try to prop up its market share for the rest of this year until its WinPhone devices are ready.

Nokia has no long term commitment to Qt. It is committing to Microsoft.

Rodrigo says:

Aron

Explain me how Nokia intends to disrupt something on software if they are actually leaving the software development to someone else and focusing on hardware?

Explain me why this disruption wont come from Google, Apple or MS that have a long road of know how and will keep their focus on that more and more to make the next disruption?

Very Unconvinced says:

This is directly from the new releases. “Elop said the partnership would mean job cuts around the world, while research and development spending would also be slashed”. So, how does QT not have an enormous bull’s eye on it?

Seriously, is this not obvious to everyone?? Out of the gate, there is a firm agreement not to have a QT port to WP7 (which is the whole point with QT everywhere, project Lighthouse). This would have made tremendous sense since it would allow developers to recoup existing QT investment on the new platform. The fact this wasn’t done should be a huge billboard advertising to all that Elop is taking his orders from Redmond on this one and it’s only a matter of time until he lets the other show drop and eliminates this part of the R&D budget…

chester says:

ha ha ha ha ha it’s all politics at Nokia now.

many nokia fans/lovers were baptised inton Adroid community yesterday after Stephen Elop revealed his political Identity,

Symbian is on a death path now.

Even if Nokia releases a MeeGo phone it’s likely not 2 get support in the long-run.

I was 1 strong Nokia fan but after yesterday I had 2 jump 2 another boat – Intel.Intel is my only option now and they have re-assured us of their commitment 2 MeeGo,and are having many big players like BMW,AMD.

RIP Nokia & Microsoft.

I’ll be get my next phone from Intel with Medfield SoC running MeeGo.

Raine says:

Ab insider i think you forget that in the end qt & meego are not Nokia’s they belong to their respective communities.

markc says:

It’s all very well for Nokia employed Qt staff to say “come on guys, stay on board with us” because they have jobs and a small part of their job security depends on the rest of us non-Nokia employed Qt enthusiast becoming and staying involved with Qt. If those that are not already gainfully employed using Qt all cut and run to webOS and Android then that move in itself jeopardizes not only the viability of Qt within Nokia, and therefor the jobs of Qt deployed Nokia staff, but also gives the anti-Qt lobby (M$ etc) more leverage to say “see, we told you Qt and that open source strategy was going nowhere” and sideline it even further out of existence.

If there is no prospect of mainstream Qt/MeeGo/Symbian products for non-Nokia Qt devs to make money from then there is NO FUTURE for Qt for Nokia outsiders, ie; the rest of us herein bemoaning this stab in the back. Trying to dangle us along with a “promise” of one MeeGo device sometime later this year as a toy, to insure Nokia with a failsafe future software ecosystem if this WP experiment fails, is nothing short of an insult to the rest of us. I have loved Qt ever since it gave me system wide anti-aliased fonts in v2.03, and seeing I refuse to touch Java, today I downloaded the webOS SDK and will tearfully poke around to see what I can make of it (NodeJS is a good start.)

So can you Nokia insiders appreciate the awful dilemma that this Elop inspired disaster has given us? We love Qt, we want true Qt/QML based MeeGo devices yesterday, we want security knowing Nokia is behind us with Nokia scale product inventory but Nokia just stole that future from us and now we also know if we walk away it’ll kill off our beloved Qt quicker than ever. Cruel. And exactly what would suit your new found overlord in Redmond. The suckiness of this situation for 10s of thousands of current and future Qt/QML devs is almost beyond belief so please don’t patronize us.

J says:

I’m quite concerned about how WP7 supports other than Windows PCs in development and usage point of view. Do we have to buy Windows in the future to be able to use high-end Nokia phones? That’ll be the last nail in Nokia’s coffin.

chester says:

ha ha ha ha ha,it’s all politics at Nokia now.

many nokia fans/lovers were baptised inton Adroid community yesterday after Stephen Elop revealed his political Identity,

Symbian is on a death path now.

Even if Nokia releases a MeeGo phone it’s likely not 2 get support in the long-run.

I was 1 strong Nokia fan but after yesterday I had 2 jump 2 another boat – Intel.Intel is my only option now and they have re-assured us of their commitment 2 MeeGo,and are having many big players like BMW,AMD.

RIP Nokia & Microsoft.

I’ll be get my next phone from Intel with Medfield SoC running MeeGo.

JoeHTH says:

You Microsoft hating, open-source sycophants need to wake the hell up. Have you not been paying attention for the past 3-5 years?

Here are the facts. Nokia has spent years and wasted billions on the development of Meego, Symbian, and Qt, with absolutely nothing to show for it. Their market share is sinking fast. They’re losing revenue. They can’t continue to sit by and watch their company suffer and decline because of shitty software or to appease a bunch of open-source fanboys.

As for Symbian? It’s a mess. Hell, Android is a mess, despite it’s success. But Symbian is a far bigger mess. It has done nothing for Nokia. As for Meego, it’s simply vaporware. Nokia doesn’t even have Meego phones for sale.

They went with WP7 and Microsoft, because WP7 is an incredible platform that brings some incredible services, UI, innovation, and usability to the Nokia phones. Services like Bing, Bing Maps, Office, Xbox Live, Zune, One Note, and so on and so forth. Nokia brings services like Ovi Maps and NavTeq. There are already over 8000 apps on a platform that’s not even 4 months old. That’s a faster rate of development than Android experienced. At that rate, WP7 will have 50,000 apps by the end of the year.

Microsoft is also the lesser of two evils, believe it or not, when compared with Google. For Christ’s sake, Google collects the private data of American citizens and sells it. I’m not sure you can completely trust any corporation. But do you really want to sell your soul to Google? Not to mention the fact that they can’t even create an OS that can scroll smoothly. Adopting Android would simply be another vendor in a sea of Vendors. That does Nokia no good.

So I understand your disappointment. But what did you expect Nokia to do. To continue to go with Symbian, Meego, and Qt? They would have continued to decline and they’d be facing bankruptcy, or extinction, in another 5-7 years. They had little choice but to change. They made the right decision.

If you hate Microsoft with such a passion, then there are plenty of other open-source platforms you can support. Android is a perfect example. It’s also an ugly, unintuitive, choppy, laggy, fragmented pile of crap. I know because Android was my first smartphone.

JoeHTH says:

By the way, there was precious little developer interest in Symbian, Meego, or Qt, at least from the development community outside of Nokia.

As for the talk of Intel and Meego, they have nothing. They have no partners. Noting, zip, nada. So don’t hold your breath.

FrenchDev says:

I had grown to respect Scandinavian software development.

But too much partnership with the americans is too much.

Raine says:

Joe, MeeGo is Linux

AntiJoe says:

JoeHTH is trolling:
> They went with WP7 and Microsoft, because WP7 is an incredible platform that brings some incredible services, UI, innovation, and usability to the Nokia phones. Services like Bing, Bing Maps, Office, Xbox Live, Zune, One Note, and so on and so forth

Bing ? wtf are you on?

OpenSourcenist says:

@Yuvraaj Kelkar: Elop explicitly said that development happens with microsoft tools. I would not be surprised if the contract between nokia and microsoft would state that QT is not allowed to windows phones

markc says:

“Nokia doesn’t even have Meego phones for sale.”

Hah! We know this M$ deal was hatched at least early to mid last year and since that moment any hint of a “MeeGo device by the end of 2010” was dead and buried. So now Nokia is in a position where it has no MeeGo devices and no sign of any WP7 devices for another 12 months. WTF! And they want to turn around their high end smartphone presence!

There is no question Nokia internals needed a massive shakeup but not having any viable high end phones (yes, plural) at all until 2012 has got to be the dumbest mobile strategy ever. Even basic things like monthly updates to Symbian on the N8 to make it a passable excuse until MeeGo (or WP7) was available is not on the agenda. And that’s fundamentally because the core direction of Nokia was corrupted maybe up to a year ago.

“[Nokia] facing bankruptcy, or extinction, in another 5-7 years”

Yes, they may very well be now.

P says:

@AntiJoe
“Bing ? wtf are you on?”

He’s on MS’s payroll.

Gordon Freeman says:

Personally I’m not really too fussed if Qt doesn’t make it to the mobile space as I develop for the desktop (where Qt is unrivalled), but if Nokia had gotten their arse in gear and concentrated everything on MeeGo I think they’d have had a clear winner. But they were too slow and it’s too late for that now.

So, let’s peer into the crystal ball and imagine that Nokia severely reduces or stops funding of Qt development in the future, after their Windows based products have hit the market. To not even ponder that possibility I think would be like walking around with blinders on your eyes after this recent announcement.

What I’d like to know is if that does happen further down the track, will the Qt developers at Nokia leave and go somewhere else to ensure continued commercial development and support for Qt? Because if we can’t be assured that Qt will have continued funding for development over the next few years, then now is really the time to jump ship to something that has a certain future.

I realise Qt will always have community support due to it being LGPL’d, but if there’s no certainty of fulltime paid development backing the framework if Nokia pull the plug, then that is a big worry, and I think this concern should be addressed by one of the Qt developers.

Also, I’ll just add that you have my sympathy… it must feel like a kick in the nuts right now.

Nes says:

Joe,
your comment is absolutely useless.
You seems to be happy… can you understand that there are lot of people worried about their own job?
I am not a google fan on, but you really do seems a microsoft fan. All the corporation are driven by/to/for/on money and profit… but Microsoft is the most stupid one.
The world gains nothing from this “new-strategic-direction”: cut on coders… reduction in r&d. It’s stupid. Just stupid.
Sorry to say but seems that who need to wake up is just you.
I think your idea is (like microsoft) passed and arid.

RobertC says:

Developers need to remember that being open source and ‘free’ does not guarantee success. Nokia has been promising a credible response to the Android and iOS onslaught for years but has failed to produce a single competitive device. MeeGo is still yet to ship on a Nokia device, while Symbian is dying a slow death despite billions of investment. Elop is completely correct to focus the battle on ecosystems because that is wha will determine the success or otherwise of companies in this industry. Ovi has had some reasonable success but it pails in comparison to Apple and Google’s efforts. Microsoft’s latest effort promises something very competitive, particularly with Xbox, Office and Bing coupled with a fast-growing app market. These Microsoft services have plenty of consumer credibility, much more so than any deal with Google would have provided.

I am currently a user of the HTC Mozart and I can’t wait to see a Nokia WP7 device.

Jason says:

I second and third Gordon’s comment. Nobody should be fooling themselves here: Nokia will only fund QT up until the point where they’ve transitioned entirely to WP7.

So what those of us on desktop platforms need to know is: do we jump ship as well? Or do the Trolls have an exit strategy that takes them through the **altogether certain** prospect of Nokia’s eventual de-funding of all QT development?

So please! Give us a roadmap. Give us a post-Nokia “hypothetical” strategy! It is insane for us continue to invest lots of time and energy in a platform that Nokia
WILL HAVE ON THE CHOPPING BLOCK in at most 2 years. Without that you are going to see developers abandoning in droves. I know I will, and that thought really depresses me.

Simon says:

The fact is Nokia has no hold of itself. If you thought the external messaging is poor, the internal messaging is even more alarming. The employees are as clueless as we are as to the future. In fact, do you know that that the Qt team is hiring? Heck, I even know for a fact they are looking for hiring new community managers! This has nothing to do with Qt having a great future ahead. It simply has to do with the fact that Nokia’s internal messaging is zilch and everyone is clueless.

So, let’s stop the bitterness, shall we? WP7 or not, Nokia was going to die; their management and employees are simply not up to the task. If you had wet dreams about a MeeGo phone, it’s because you haven’t used MeeGo. I mean even the Nokia employees point at it and make fun of their MeeGo prototypes. So, this decision about WP7 is actually irrelevant.

Simon Colbert says:

The fact is Nokia has no hold of itself. If you thought the external messaging is poor, the internal messaging is even more alarming. The employees are as clueless as we are as to the future. In fact, do you know that that the Qt team is hiring? Heck, I even know for a fact they are looking for hiring new community managers! This has nothing to do with Qt having a great future ahead. It simply has to do with the fact that Nokia’s internal messaging is zilch and everyone is clueless.

So, let’s stop the bitterness, shall we? WP7 or not, Nokia was going to die; their management and employees are simply not up to the task. If you had wet dreams about a MeeGo phone, it’s because you haven’t used MeeGo. I mean even the Nokia employees point at it and make fun of their MeeGo prototypes. So, this decision about WP7 is actually irrelevant.

marshall says:

Turn into an open source company and everyone will like you. You’ll also end up like Sun.

BTW, if you think is Google is so FOSS friendly, ask them for their search engine’s source code. Good luck.

markc says:

“Symbian is dying a slow death despite billions of investment.”

I’ve seen this rehashed a number of times as a reason to dismiss Symbian. Of course Nokia has spent billions on Symbian, there are 1/2 dozen currently supported versions on 100’s of millions of device for the most part of this century. What is a fallacy is to equate those billions as being spent on modernizing the latest pre-Qt S^3. To infer that is so untrue as to be a lie.

“[WP] coupled with a fast-growing app market”

But… but, OVI is ALREADY one of the largest app markets on the planet. And your point was…?

“These Microsoft services have plenty of consumer credibility”

Whoa there, big words. That *may* be the case down the track but so far WP7 sales have not been all that stellar. I’d love to know how many N8 devices have been sold in about the same time frame.

NuShrike says:

This is your well deserved karma reflecting your incompetence back at you!

I’m a developer of at least 23 years of experience in console gaming, dot.com, online games, graphics/opengl and embedded devices! But what does that mean for you? You told me to go away! You probably called me a troll internally.

I had submitted Windows Mobile 6.5 patches to Qt because I was doing serious work on it with Microsoft “away” working on Wimpy7s. You ignored my patches; nitpicked that you don’t see the value in them (significant footprint savings) or the “tabbing was wrong”. I had patches that unbroke WM6.5 building, that enabled access to the new LayerWindows API, fixed issues with Qt3D; you IGNORED them! They’re probably sitting in JIRA after almost a year now!

I’d pointed out how bad QtCreator’s memory footprint was getting vs MSVC or the original QtCreator 1.1. You couldn’t invalidate the JIRA ticket fast enough after ONLY testing in MacOSX when I pointed out it was also Ubuntu and Windows. And you still ignored it.

I pointed out on Twitter how detrimentally Nokia-centric Qt had gotten especially with the Mobility SDK and it was perilous to ignore other platforms such as Android and WinCE. You independently made a short blog about how awesome webOS Qt could be instead; and then you announced no new platforms would be added to Qt. So Lighthouse is just a DEAD figment.

You’d also told me to go try talking to the “developers and community” when they’d already shut me out in JIRA.

I’d pointed out how bad Qt’s footprint is in WinCE with its limited 30MB of virtual, and that footprint is unacceptable even for the other professional embedded projects. You told me the blog was not a place to voice such complaints, and then you ignored me.

You’d announced how Qt was going modular, and I’d asked is it going to break out legacy widget code in QtCore and QtGUI so embedded can use it without your HUGE footprint > 12-15MB. You told me to use your broken qtconfig (since 4.5) when I said I used it. Happens you were only going modular for your git repos, and you told me to go away.

Now I’ll add that that Wimpy7s is all about .NET and Silverlight. Qt is 100% C++ (poorly and your choice to not use WTL and WPF’s style of templating now haunts your footprint and class hierarchy with Qt Quick a poor hack emulating it).

Somebody could create .NET bindings for Qt, but Qt cannot be written on the Wimpy7s platform PERIOD. There’s NO NATIVE APIs and that’s the core of how Qt works. I’ve done enough .NET coding to know you DO NOT want to marshal between .NET and native in the same way you don’t want too many JNIs as it sucks cpu cycles and bus bandwidth.

I gave up on you professionally and personally, and moved over to Android. Your Nokia positioning (moving all your servers over, being Nokia centric in development for at least over a year) has been your poison pill.

Now you should go away.

Anonymous Coward says:

@NuShrike

Are you dumb? You post will be read as: I made poor quality code and you did not accept it, please make fun of me 🙂

NuShrike says:

Anonymous Coward: if that’s the only valuable strawman you can take away from this, so be it.

I know the quality of my code, I can byte-count the footprint savings in the drivers I’ve written and am now writing, I’m now an Android kernel hacker with published GitHub repos, and the original evidence is fully-documented in JIRA.

Robert Xu says:

We forgive you this time, Nokia.
Just next time, remember about us FOSS users.

markc says:

“I mean even the Nokia employees point at it and make fun of their MeeGo prototypes.”

That probably has more to do with the fact that Maemo based devices had been around and well tested for a couple of years and then somehow Nokia got sidetracked and started from scratch yet again with MeeGo! So sure, the first MeeGo prototypes, compared to established Maemo devices, were probably a joke. I’d blame that one on whoever decided to dump Maemo, an almost complete OS that just needed Qt and a bit more time (from 2 years ago) to mature as opposed to “let’s start from scratch with a partner who doesn’t even support mobile CPUs or Qt that we just invested in”.

In fact it was probably this move that was the straw that broke the camels back. We could have had Maemo 6 on a N901 device a year ago for a fraction of the cost that has been spent since. Both incremental updates to established hardware and software. A N901 only needed an overclocked cpu, a bit more ram and a capacitive display with a snapshot of the latest Maemo… done… a year ago. That could have done the job of the mythical N9 with MeeGo, that we’ll now probably never see, and got precious hardware into the hands of Qt devs that so desperately needed something yesterday, and not just emulated promises.

NuShrike says:

That’s Gitorious repos … and I’m a established WinMob dev. Those know what I did for the Kaiser’s drivers.

Buffy says:

We shut down our company QT development last fall in anticipation even though nokia was selling QT rigorously. Yes, the developers were extremely pissed for about 2 weeks. Rarely these guesses go correctly but in retrospect it seemed to be the right one.

As likely projection go, Stephens only job is to trim Nokia down for a sale for Microsoft and wintel. Google and Microsoft would like to be more Apple, and hence Google we saw phone attempt. Microsoft has positive experience from XBox and they wish to avoid the pitfalls. They will eventually go for own hardware way regardless if this means killing their existing partner ecosystem. As HP had shown, there is no loyalty in hardware relations, it is just business. The only thing standing in the way is anti-trust legislation.

In this environment, QT would most likely be span out from Nokia, but not forgotten.

toran says:

Buffy,

If your company does desktop development using C++/Qt and it stopped using Qt – what it was replaced with? Just curious 😉

lou per says:

So what’s the Qt development team’s strategy when Microsoft buys Nokia in the future (as has been discussed in many news articled associated with this whole thing)?

Those of us who have built shipping cross platform desktop products based on Qt are watching this whole thing with some trepidation (to say the least).

I serious hope the old Trolltech team is plotting some future scenerio plans to keep things going as a new separate entity when Nokia dumps them over the side of the sinking ship. As a developer whose business now depends on Qt’s continued development in the future as a cross platform desktop and tablet framework, i’m very concerned and worried.

Desktop developers seriously need to transition their existing products to also work on tablets and other mobile devices. My hope was that Qt was going to evolve into the tool to enable me to achieve this goal. Now i’m more concerned about whether my investment in Qt as a cross platform desktop framework will still be viable 2 years from now, as opposed to hoping it is going to enable me to transition my existing products to mobile devices.

Trolltech and with it Qt development being spun out again as a separate company would make me (and a lot of other people) sleep a lot easier.

Byffy says:

Toran: We are doing mobile and web. The decision was relatively easy since QT 4.7 was dropped out of last year Nokia releases (like N8). We shut it down and went with webkit (which has it’s flaws). Nevertheless the transition to WinMo is easy.

Personally I think that the Troll’s were pretty much the only competent division in Nokia software wise. The decision to overhaul OS headers perhaps questionable or did not sit well with me (they should have left simian-os as is and focus on the UI layer only). Given how things are proceeding, it does not matter much what we debate here.

Phil Lejeune says:

Back in 2003 we were coding with C++ with MFC and running it under Linux & Solaris re-compiling with MainSoft WinMain product. In 2003 Microsoft invested in that company…and made sure to kill the product (remember in that time Linux was a ‘cancer’ to Microsoft). Same will happen again to QT if QT doesn’t return to a free spinoff company, namely Trollteck. If this doesn’t happen, we’ll simply need to switch again to other tools were Microsoft strategy doesn’t mater. What’s for sure: QT within Nokia and with Microsoft around is in a dead end; no matter what PR people say; it is simple business sense.

Mario says:

“Resistance Is Futile, You Will Be Assimilated”

GreyGeek says:

I began using Qt before v4 was released, using a commercial license from Trolltech. Their support was excellent, and so was the tool. Under Nokia it has been *significantly* improved with enhancements: QtCreator, QML and Qt-SDK, all under the same licenses as Qt. I used MS VS C++ 6.0 with Qt Integration on XP for development but found that using Qt on Linux, with Kate as the editor and Kdbg as the debugger, was more than TWICE as productive as Qt on XP because the Linux environment was that much faster. When QtCreator was released I switched to it and found that it is equal, and in some way superior to MSVSC, and Qt4 is now, IMO, the best toolkit on the planet for Linux, Mac or Windows.

I can understand why Elop, the 7th largest MS stockholder, would want to kill Nokia’s influence on Qt. However, Nokia giving MS control over their hardware in NO WAY diminishes the usefulness of Qt, except on a Nokia WP7 smartphone. Sorry Elop and Ballmer, Qt isn’t going away!

While Qt IS used for development on XP, VISTA and Win7, I don’t expect Microsoft to make WP7 compatible to Qt, and I don’t care. WP7 isn’t going anywhere. With all their marketing clout, and even their bag of dirty tricks, Microsoft has managed to grow WP7 at only about 1%/month. It this rate it will take them only EIGHT years, almost three computer generations, to capture the smartphone market. The public yawned at WP7’s release. They are still yawning. Exploiting Nokia won’t make WP7 better. The public will be yawing in 12 months when WP7 (notice I now don’t have to mention Nokia?) finally reaches 10 or 12%, IF it ever does. Nokia might not survive this “partnership” any better than Novell did, but I hope they do. With Elop as the CEO, however, the odds are against them because Elop’s focus is on his own stock portfolio. (BTW, Did you notice the similarity in the photos between Ballmer + Hovsepian and Ballmer + Elop?)

But, contrary to all the negative postings here by MS sycophants and Technical Evangelists who claim Qt is dead, nothing could be farther from the truth. It is alive and well and will continue to thrive and grow. Nokia even provided for Qt in the “Free Qt Foundation” document, which quarantees the survival of Qt regardless of what happens to Nokia:
http://kde.org/community/whatiskde/kdefreeqtfoundation.php

So, newbie Qt developers, you haven’t wasted any time in learning how to develop using Qt because learning how to use it wasn’t that difficult to begin with, so good is the toolkit and its API, and you now have at least three platforms where the same tool behaves the same way on all three and you have to do your work only once. The .NET/Mono Silverlight/Moonlight tool chain is not even close to Qt’s breadth and depth, and it is not plagued with EMCA 334 & 335 restrictions or potential WinForm patent violations. Were you planning to become a millionaire by selling 5 million copies of your “Angry Birds” Sybian/MeeGo clone at $1 each? If it’s that good there is a bigger market out there than what WP7 offers. You’ve left the MS plantation. Look around. It’s a big, FREE world out there.

Ilgaz says:

Somehow the entire developer community lost their trust to nokia, even including windows developers.also one of the top game developers (top of the top) called symbian “dead” on twitter.

Keep dreaming about 150M sales.

Buffy says:

Symbian is deader that Elvis, even Nokia folks seem to agree on this.

sprata says:

I share the concerns that lou per has. We develop cross-platform Qt applications and in the mid- to long-term also want to have embedded front-ends. We have new projects in the queue and with the current announcements it seems that Qt would be a rather problematic choice.

As for now it really seems that Qt will be phased out in the next two years (those 150 million low profile devices are no help there) and all the good talking does not change that. Elop made it quite clear that Qt has no real future as it will not be ported to WM7 and half of the people working on MeeGo will be fired (look at the slides…).

Also the “community” or “KDE”-approach of a phased out Qt is not an real option for professional and commercial developers who depend on a full paid team that develops Qt. Especially when we have this great team that works on Qt now.

I really hope Intel steps up and makes Nokia an offer to buy the Qt Software devision. I don’t see much alternatives and Intel would be a much better partner than Nokia anyway in my opinion.

So please Trolls, try to get in touch with Intel as I *really* can’t see any future with Nokia and the radical layoffs that are planned for you before it is too late and your great team is leaving and going to work for Google (or HP or whom ever).

qtnext says:

With Intel, you loose ARM market … and it’s in fact far more important than Intel On mobile…
I agree with you about “community” or “kde” .. it’s not enought for a good commercial products : it’s need a lot full time payed developer to continue to innovate
and for sure, the power of Qt is cross platform : so trolltech need to go out in a company where it’s ok to target all desktop and a maximum of mobile platform …
but what will do other in the future :
– Apple : close Qt to IOS, but With apple market, perhaps the next step is to lock mac Os to ObjectiveC native application.
– Windows : WP7 … .net for sure no acces to Qt… But what’s about next Windows Version : .net Only with app store ?
– Android : to allow Qt, google need to have to include Qt Lib … will google do that or prefer lock the platform …
– Linux : Ok …. but for commercial apps .. it’s for the moment quite limited …

Clearly a bad day of Qt…. Sad

MH says:

I am sory for all the engineers working with Qt/Quick now…

There is only two worlds top Nokia! SELL QT!

No appdeveloper can trust in QT now when Nokia is sold too a closed company like Microsoft! They will ruin the company 🙁

History had show this before!

Tom says:

Trolls: It doesn’t matter if you keep working on Qt. It doesn’t matter if you make it even better. Nokia killed the future of the Qt ecosystem and thus made Qt irrelevant to (mobile) developers no matter how good it actually is. It’s not a war of frameworks, it’s a war of ecosystems and Qt’s just got flushed down the toilet. I would consider the move to WP7 a smart one if Qt was supported too. But like this it’s nothing but surrender without a backup strategy. Qt was on the rise, now it’s on the downward spiral. Dammit, listen to the feedback you get everywhere – it’s a mess. Nokia spit the community in the face. If something stinks like a dead fish it most likely is one…

Time to move on.

Another voice says:

I haven’t seen a relevant Meego or whatever mobile device that uses Qt aus a UI until now.

So frankly, I dont care.

There’s nothing lost. Just continue development for Win, Linux, Mac primarily

Fantomas2006 says:

Now that there are 3 or 4 or … mobile OS (iOS, droid, wp7, …), it would be nice to have a (true?) Qt mobile framework. “write once, run everywhere”. No need to learn objectiveC + java + c#

test says:

MS, we know you and watch your sabotage to laugh at you.

Plz can somebody leak the email from-to the Elop-MS-shareholders-etc ! It would be fun to read that stunt and hopefully used to educate that poor next bastard who’s infested by MS viruses. May be it’ll contain things like that:

MS How-to #123: Wipe our your future competitor (nokia) strategy.
————————————————————————————————-
step1) Turn shareholders brains into “yeah, we’ll be making more money” if you do what we say. Check: Brain guards in off-mode.
step2) Plant your best man as next CEO. Check: Brain is under control.
step3) All top level ppl are told they’ll go when they make problems. Check: Virus control is virtually dead.
step4) Let your pet analyst plant stories how good it is that you will come. Check: FUD. Yeah, also the analyst said it’ll be ok.
step5) CEO: Make up stories of how urgent the situation is and jobs will be cut, if so and so. Check: Mouth-dead the employees.
step6) Rip-off all guts and nerves (symbian, qt, ..) of the infestes corpse and use what you can get.
step7) Assimilate technology that can make you stronger. Totally destroy technology that could grow up and challenge you (Qt!). Check: Strenghten up for the next host/fight. That’ll be Apple or Google, when they are not carefull.

That is just so cheap, no honor. That brutal/aggressive social shit tactics to cover your incompetent’ness. To movie “pirates of the silicon valley” is so true about the MS character.

Nokia, bye bye.

Canonical already said they will ship Qt by default with the next release of Ubuntu. I think Canonical should do more than embrace Qt, they should buy Qt (TrollTech)!

They will gain my eternal respect by doing that. I’m sure other Qt Developer will share the feeling. 🙂

business as usual says:

Real work happens on good old desktop computers and that’s where Qt belongs and matters.

Smart phones are toys. Tablets are a hype.

Ask yourself: if all smart phones stopped working tomorrow – would anything change except people wasting less time with them? There you go…

@Another voice: I haven’t seen _any_ relevant mobile device so far 😉

Htoo Myint Naung says:

Nokia is a parasite that infected awesome Trolls. Really hate to see such a great thing like Qt die by some strategy makers’ decision.

polos says:

@business as usual: exactly!!

Most of real science is growing very, very slowly, and most of computers are used for 99.99% superficial/futile/chimera stuff…

🙂

Toni Nikkanen says:

Is there any technical reason why C++/Qt apps couldn’t be statically compiled to the .NET CLR? They would then run on any WP7 device, thus fulfilling the “Qt Everywhere” promise while not causing (runtime) fragmentation either.

Microsoft tools already promote this idea that you can use almost any language on top of the common runtime, from C++ via C# to Python and many obscure ones as well..

Buffy says:

Nokia will not spin out QT until MS tragedy has succeeded, they must have a backup plan in case things do not work out – a principle of corporate thinking.

sprata says:

@qtnext, I don’t think that ARM support is that problematic when Qt would be owned by Intel. Most of the performance optimization and footprint reduction is relevant for all architectures and all platforms will benefit from improvements in that area. The specific ARM-code parts are too small too really care about as a whole (some in-lined SIMD-code maybe….).

Thus I think Intel is still the only really viable player to get hands on Qt now. And something like Canonical is just absurd. Nokia bought TT for $150 mio. and Canonical has a revenue of $30 mio. that just does not fit….

I really hope Intel comes out as I predict it to be the ONLY option Qt for professionals and commercial developers has.
In the KDE/Open Source field it all does not really matter there is an ample exit-strategy (like merging it with kdelibs), so all those particular arguments are not relevant for the industries using Qt as toolkit for proprietary products (or even OSS ones)… and I doubt the KDE community will administer an BSD-based Qt instead of an LGPLed (as commercial licenses are still relevant for many Qt customers and LGPL just won’t do for various reasons).

As much as I try, but I can’t see any sustainable future for Qt with Elop at Nokias head. He has other plans that is for sure now.

Indeed a sad, sad time for Qt…..

Christopher says:

Wow congratulations to Nokia for shooting themselves in the foot!

WP7 is garbage. As a Long Time user of windows mobile 6 I had faith in M$’s mobile system, if not their execution (lack of updates). However, when WP7 was announced with no support for native development M$ shot themselves in the foot as well. For two companies that have had their issues with getting their product/updates out to the users, I’m truly concerned for Nokia’s future.

As for Qt… The direction is clear!
The best thing for Trolltech and Qt is to get bought out by another company. Who you might ask? Well obviously Intel. Intel had big plan with Moblin before Nokia entered the picture. Now a year after the announcement Intel has held up their end and Nokia has failed on its side. Intel still has big plans for In-house electronic systems. Meego and Qt fit this equation. Intel has announced its not giving up on Meego and its time for Qt to move on to a serious player. Intel please buy Trolltech/Qt and increase your continued support of open environments, we will pay you back!

M$ has too many old men at the top to see what my generation (Y) will achieve. Luckily they have had enough money from windows and some from xbox to fail miserably on windows mobile and wp7. Not to mention the Zune Hd is garbage and anything but HD. Also did anyone here of the Kin? So Nokia and M$ are gonna team up to take on google and FAIL.

Apple will continue to do its own thing. And webOS will have more focus on embedded application and tablets than phones. Intel needs to find a (smartphone) OEM without a financial thumb up their arse, and make them partners Asus/lenovo maybe? Then make a Meego device with a Keyboard that rocks (maybe using Hitachi’s new IPS screen?)! Tablets are nice but people didn’t want an IPad before they bought their IPod or IPhone. You need products that will get into peoples pockets to create loyalty.

As an American I feel M$ has been making a lot of bad decisions (except with windows and maybe Xbox) lately. And this will eventually show in revenue. Everyone who has experienced the tight grip of M$’s WP7 has chosen to FOCUS on Android (Samsung & HTC…etc).

@business as usual ….Smartphones will only be toys for another couple years. Just wait a new era will come.

Elviin says:

Here is a post related to the Intel-Meego relationship:

http://appdeveloper.intel.com/en-us/blog/2011/02/11/intel-and-meego

Tom says:

this is interesting:
“Re: Qt: Stay tuned for more details.”
quoted from http://appdeveloper.intel.com/en-us/blog/2011/02/11/intel-and-meego

qtnext says:

to confirm .. Elop is the 7 personnal shareholder … a good day for him
http://www.dailyfinance.com/company/microsoft-corporation/msft/nas/institutional-ownership

seems this world is walking on his head 🙁

JakubK says:

This is for sure not a best day in Qt’s history, however remember that all this “mobile future vision” of Qt started when Nokia came in. Before Nokia, Qt was targeted mostly as multi platform desktop development and dedicated embedded solutions, and hey – it is still there and is strong! When blaming Nokia for marriage with Microsoft, keep in mind that they invested a lot into Qt and what is even more important, it was Nokia who moved Qt to LGPL. TrollTech before was strong company, but Qt development in its best Nokia times was really dynamic. Just track Qt4 development speed and how many great features were add then. Same time I would not blame Qt for MeeGo’s fault.

What Nokia did is also sad for me personally however, Qt was not only raising platform or ecosystem for Nokia phones. It is also so called “last hope” for keeping C++ development really popular and important these days. In my opinion programmers nowadays are not interested in performance or language flexibility so much. Most of us know that C++ is powerful and great to use development language, especially when combined with Linux, but that does not matter when it comes to rapid development of enterprise or mobile applications. Surrounded by other major players (Java and .NET especially), C++ in most cases requires still more competence from programmer, and competences cost. Moreover it is a lot easier to shoot yourself in the foot in C++ than in Java or .NET…

Even if Nokia will loose its interest in Qt as mobile development platform in a year or two, Qt will stand in C++ world since there is no real alternative. It is reality that developers do like Qt. I program in C++ for a living. I really enjoy this and Qt makes programming in C++ one of the best development experiences ever. So, be optimistic, in embedded or development world nothing changed, Qt is still strong player and it will prevail for sure. 🙂

eMPee584 says:

EEeEEEEEwWw that is so0O grO0oss. I never liked symbian much, and the one nokia phone i ever posessed scared me away when eventually the internal RAM ran full and there was NO way to boot it up again, neither to pull the data from the internal memory – i had to reflash it (loosing all data!), and ever since had been a happy SE W800 user (w995 since last year)…
Using (gent0o) linux on my workstation, and a lot of qt based software, i salute! the TR0LLTECH team for their quality software engineering skills. MeeGo with QT always sounded to me like THE most promising thing – a completely open platform where i’ll finally be able to customize the behaviour of the hardware I PAID FOR fully to my liking.– Now this.
Truely sad Nokia got trapped by that win32.elop.trojan. One must ultimatively ask: are they mad? Did they even have a serious investigative strategy review, together with their software engineers and designers before they made this bonkers decision? Everyone with some technical expertise must have been able to see the potential of QT/MeeGo – on the one hand technical merits, on the other hand the promise of attracting the huge lot of developers sick of vendor lock-in and propietary and non-customizable software platforms. And that still holds true and will make this combo a success – if NOKIA doesn’t do it, the chinese surely will (no licence fees, complete adaptability – go figure).
What the fsck have senior managers been smoking there.
Rise up, nokia employees, get rid of that elopjerk!! REVOLT! Egyptians did it, so can you ^^

oiaohm says:

Also MS kinda said that Nokia would be able to alter Windows Phone 7 how they see fit.

Shipping with support for native programs done in QT in Windows Phone 7. Would prove to us that Nokia has not given control of there platform. QT is the toolkit on everything else Nokia makes. This is simple constancy and cost maintenance.

The damage to Nokia share price is partly that it appears that control as been given up.

Tom says:

imo Intel should team up with HP and get control over Qt (fork it if necessary). Intel needs it for MeeGo and and it would be great for webOS too (webOS will even supplement Microsoft Windows on PCs in the future). Oh, and get as many trolls on board as possible.

Bill G says:

I think their is a law in Norway and in Finland about foreigners destroying the national assets. This time we could stop Microsoft from operating through law suits.

serkol says:

In today’s news: Nokia brings in second Microsoft exec as North America head

Did MS ever liked anything cross-platform? Isn’t it clear to everyone that Qt has NO FUTURE with Nokia?

Emilio says:

I followed Nokia mistakes since nokia 9100 and N-Gage, I want to explain how can nokia solute the competition problem, and get a new SOFTWARE environment, contact me pleas and I will give my ideas for free, as you wil make a great change and challenge in the world with this move good for all humanity and health.
Pls do it,
Pls Open QT to Android and IOS4, WP7 is not relevant by now, is only future as MS is sinking with OPENOFFICE and many more.

The solution is QT compile automatcly all sources plus Android+IOS4. And publishes it almost automatcly.

You know why:
Easy, because most devs are producing for IOS4+Android, and if they have 300.000 apps in IOS4+Android, you will get your 300.000 apps for SIMBIAN&Meego, as devs would not headache to produce with ZERO effort, same APPS what they do for earning money in IPHONE, saved AS nokia-apps.
So you would solute the Nokia-apps MARKET SINKING PROBLEM.
Why will success WP7 if it is not succeeing right now, what is it doing better? they have hundreds of phone brands, now NOKIa will offer one hundred more. Same than HTC-samsung-sony–. Nothing new…

See what is happening with Office-killer Openoffice Save-As, same will happen with WP7.
sorry for nokia is burning so many millions EURO into wrong strategic.
These millions belong to the world not only to NOKIA.
ciao

Shmerl says:

No, I strongly disagree that it’s wise not to port Qt to WP7. The only reason MS doesn’t want to ship an NDK with WP7 is to retain their control over developer tools. I.e. they want people to pay for them. Nothing wise except money hungry MS interests. Nokia betrayed Qt developers when ditched Meego as a primary focus, and not forcing MS to ship an NDK for WP7 which would allow porting Qt there. What a shame.

Emilio says:

@serkol cross-plataform like SAVE AS MSDOC.ODT/MSDOC.DOCX

You get cross-platform office suites crashing MS-OFFICE versión.

What are this OFFICE ppl seating on the big desks. Waiting for next month payment?

nic says:

What is a disrumptive, and where do I buy one for my kids?

GreyGeek says:

Nokia also announced it will ship its first MeeGo-related device in 2011, which will rely on the Qt ecosystem – and then will continue with MeeGo as an open source project for future disruption. Nokia can’t afford to be behind the next disruption again and Qt can play an important role in making sure it isn’t.

I read that as saying that THE disruptive technology is Qt and they WERE on the front edge of that wave. By retaining and continuing to use Qt on Symbian/MeeGo Nokia is wisely hedging its bet on WP7.

axel says:

Canonical doing something useful with Qt? Please… they can’t even get people to use the crap they give away.

luca says:

In my experience most of the companies developing apps think iPhone first, Android second…NokiaQt next to irrelevant. As of now why should any company even think in investing effort in dev Qt apps for Symbian and the one off device Nokia will release this year?

As of today I don’t see much room for Qt within Nokia. I hope Nokia sells it to a company that can put this fantastic framework again in the spotlight it deserves like Nokia did before the change of heart (imho Intel would be a good candidate, especially if a Meego “Intel inside” phone will ever see the light).

juancpaz says:

Nokia, f**k you!!! Stephen Elop, go to the hell with M$ bastards!!!
QT is LGPL, so, we, the QT community, will do with QT what we want. No matter the future of Nokia. We will write the future of QT and we are Legion.

(Sry for Nokia employees)

LoQT

serkol says:

@markc – I like your comments here and at http://appdeveloper.intel.com/en-us/blog/2011/02/11/intel-and-meego – very thoughtful.

One thing bothers me (this is not my business, but anyway…) – you wrote that you’ve decided to learn webOS SDK. Why did you chose the one with the smallest market share?

I’ve started my app with an early beta of Android. Eventually I got so frustrated with endless promises but no real devices and real app market (that was almost 3 years ago). I’ve got tired of spending moths of my life with no rewards. So when Apple opened App store for 3rd party devs, I’ve ported my app to iOS. It took me 1 month. 1 month later I quit my fulltime contract, and all my income comes from this iOS app since then. Yes, I hated ObjC – initially, because it’s weird, now I sort of don’t mind it. No, I did not want to buy any Mac toys, but now I sort of like them… just my 2 cents.

WeAreNotFallingBelieveOurselves says:

Please stay calm and have a clear look at yourself, where is your confidence and courage? You are not dead as the others keep saying it, it only is until you believe it yourself.

http://communities-dominate.blogs.com/brands/2011/02/why-nokia-os-strategy-is-right-for-nokia-and-shift-to-android-or-phone-7-would-be-madness-now.html

Youssef Mrabet says:

his post is just nonsense…

Even if Qt on WP7 causes fragmentation it would show Nokia’s commitment to it, and would enable Developers to continue their projects with insurance.

And why not just drop MS tools for WP7 and replace them with Qt? Wouldn’t it be a fair counterpart from MS for all what Nokia did put on the basket?

This way Nokia could keep its Store and differentiate from other WP7 licensees.

serkol says:

The former Nokia boss used to say that phone manufactures who adopt Android are peeing in their pants to keep warm.

Well, if I were a Qt Mobile developer, and decided to stay with Qt Mobile now, it would be like I am shitting in my pockets to get a warm feeling there (instead of money) 🙂

Likely I need Qt only for desktop… Intel, please don’t make me shit in my pockets! 🙂

hsm13 says:

Many times I said Qt should improved to be as a Business Programming Language. Nobody wants to hear.

I’m in bad mood since two days ago, and I hate nokia and Elop hurts a lot of us.

[Comment moderated / strong language — Alexandra]

xiaowan3 says:

i hope andriod can join qt

jimbochicago says:

OK, stop! This isn’t a matter of code-splitting; the issues are coming to light, and have serious legal implications that far overshadow our geek world. Namely, the criminality of this MS/Nokia transaction; the anti-trust violations; the damage to EU economies and Finland’s own laws. Elections are in April; thousands of Nokians walked out the day of this announcement. This is just the beginning.

Be glad that Elop and Blamer did this with such arrogance – as only American executives can, having cowed the public here to accept *anything* that corporations do, they don’t even bother to fake it. That attitude has made the fingerprints on this move so obvious, the cover story now so flimsy, that Elop is going to have his ass loaded onto the first trebuchet aimed out in the general direction of deep Baltic water. Seriously, Europeans aren’t going to put up with this illegal shit, and this is only going to make Nokia stronger. And if it does, then Qt and whatever OS(s) Nokia FINALLY settles on will be the combination that developers can loyally support. Because Android is just Google sliming its way into every pore, and Apple is its own police state, and developers really, really need something nobody’s going to lock down or pull the rug out on.
Of course, if everybody lets this travesty of corporate crime go forward, then sure, nobody can trust Nokia anymore, obviously, because it will be a name plate only, operated by MS for MS’ purposes. And being bright developers, we don’t think MS is really going to cut you any slack, right?
Let’s take a lesson from the Egyptians on this one. Support the Nokians we all love in their revolt or resistance. Evict Elop, Europa!! Just please don’t send him back here.

Kendall says:

Nokia needs to choose. Are the really proceeding with Symbian? Or MeeGo? Or Windows Phone 7?

You need to pick a direction, not sail in all three at once on a breeze of conflicting hot air.

Otherwise you will end up like Palm that couldn’t choose between PalmOS and WinCE, and eventually ended up with neither working out because they could not commit.

As a developer I’ll not touch any of those three things now with a ten-foot pole. If I had to support anything other than the iPhone right now, it would be WebOS from HP. At least they have a vision and a direction that is clear, if fraught with peril. Why can Nokia not provide that level of clarity?

Another insider says:

@An insider: Do you realize that the plans were very far along to unify Symbian^4 and Maemo to just use Qt-based Orbit? Think of Orbit what you may, but it would have reduced the fragmentation and might have even be partly folded into Qt. All that came to a halt when Maemo threw a tantrum, insisted on libdui, and essentially doomed both efforts.

FF says:

It looks mere firefighting after Nokia CEO has blown up the existing customers and developers.

Steve says:

@Shmerl
Except all Windows Phone 7 tools are free so that makes no sense. They want to maintain consistency in the user experience, and not introduce hacky non compatible code like what happened with Windows Mobile.

int19h says:

@Toni Nikkanen
> Is there any technical reason why C++/Qt apps couldn’t be statically compiled to the .NET CLR? They would then run on any WP7 device

Short answer: compiled to .NET (i.e. to MSIL bytecode) – yes. Run on WP7 device – no.

Long answer: MSIL bytecode, as well as CLR type system and command set, are flexible enough to permit a full implementation of ISO C++ targeting them. Indeed, Visual C++ can do just that with the “/clr” compiler switch – it will take practically any C++ code you throw at it, and spit out a managed binary that runs the same as native version (except it’s slower, naturally). I’m not sure if anyone ever tried compiling Qt with “/clr”, but I don’t see any particular reason as to why it wouldn’t work.

The catch is that C++ is an inherently memory-unsafe language, with its unchecked pointer arithmetic, casts, and unions. MSIL supports all these things, but using them results in what is called “unverifiable code” – in other words, the code which runtime cannot check and statically prove that it cannot, ever, corrupt memory (and thus break out of the sandbox). For .NET desktop software it’s not a problem, as there is no sandbox. Unfortunately, this is not the case for Windows Phone – it requires that all applications consist strictly of .NET assemblies that contain verifiable code only – so no raw pointers, no arithmetic; no C++.

Now, Visual C++ also supports “/clr:safe” compiler switch, which generates verifiable code. To do so, it restricts the input language to a subset of C++, extended with .NET-specific language extensions (called C++/CLI), that is verifiable. It is a _very_ narrow subset of C++, and practically no pre-written C++ code would be compilable there. Definitely not Qt.

Finally, it is theoretically possible to implement full C++ in verifiable IL – you would pretty much have to guarantee that any instance of “undefined behavior” in C++ spec would be caught and handled. This would necessitate fat, range-checked pointers, implemented as indices into .NET arrays. Theoretically, this is quite possible to do, but performance would be dismal for any practical application.

Hope this helps.

Jussi Toivola says:

The fact that you can’t use C/C++ with Windows Phone 7 will be causing fragmentation, not the ability to reuse your code. It’s fragmenting your code so MS doesn’t care. This is even worse than the Apple’s ban on scripting languages, which was removed a while ago. They still allowed reusing old C/C++ libraries, like physics engines in your apps. You can’t even use scripting languages such as Lua unless you’ll find a C# port for it.

M says:

@RobertC “Developers need to remember that being open source and ‘free’ does not guarantee success.”

But adopting WP7 without any exclusive rights, without significant market share, with no interoperability or compatibility, and without developer adoption pretty much guarantees failure.

With MeeGo, Nokia could have run Qt apps, Android apps, and Symbian apps.

Leonidas says:

I have to say that there are dumb decisions that some CEO’s make but this has been the dumbest of them all. Could someone send Mr Elop back to his beach house fast? I have to admit I did not like iPhone for many reasons. Even Android phones had its drawbacks when comparing to NOKIA. But this change of strategy ( I have lost counting in the last two years) has managed to change that. At least there the company is loyal to the customer.

What I mean. A smartphone is not just like any other device. You sell also the fact that one will be able to get applications in the future. I am just wondering how many people will continue to develop for my new N8? I am a developer and I wouldn’t .

Nice going… Mr. Elop go home.

Leonidas says:

Some people ask if QT will be ported to windows. That is like microsoft would shoot herself in the leg. QT is competing to .NET . You can see the reasoning.

aDeveloper says:

@Jussi:
That is exactly the reason WP7 will fail.
Everything but your fart app/casual game/specific rss reader will not be rewritten in pure c#.
The devs will use IOS/Android instead.

No serious game will be pure C#, especially in a world where pretty much every game is developed cross platform. and IOS/Android have a much higher priority.

The same is true of most serious business software, think of libraries for OCR, logistics, stochastics etc…
Those would not even perrform on a virtual machine + a non portable C# port would be too expensive for less than 10% market share anyway.

Pure C#/cli is not an option for a lot of applications. c#/wpf is great for frontend development and ok for some backend development, but there are strict limits.

That is the beauty of Qt. You have QtQuick and the easy javaish/Qtish C++ for the frontend and real powerfull C++/C for the backend in one toolchain/compiler.

Martín René says:

What saddens me more, is that Maemo/Meego is the only true mobile computer OS. Nevermind that Symbian supports preemptive multitasking since its inception circa ’98… not that shit about hibernating applications like Java ME, Android and iOS.
Heck, even my S40 (a 5310XM) has almost all the functions of a smartphone, it just lacks a touchscreen and wifi…
It’s now the time to mourn the loss of the best mobile operating systems in existence…

roberto says:

“Strategic direction”… but wrong one. Your stock crash has proven it. Nobody wants Microsoft.

Continue with your good phones, develop Symbian and Meego, use Android.

You will fail with wp7. Microsoft is dead on this market and will take you with them…

Please rethink this decision.

Mauro Z says:

Hi all.
Due to Nokia + Microsoft partnership, Qt in the future can leave LGPL license?
My first fear is: Microsoft may buy QT so we should pay for each application developed?

An insider says:

In summary, it appears that the board has finally lost all confidence in Nokia’s ability to deliver innovative, compelling mobile software and services to market on time.

Frankly, the fiasco over the new Symbian^4/Meego Qt-based UI, the lateness of N8 and E7 on S^3 and the non-existence of Meego products makes their fear understandable. Nokia has very serious problems with software quality, and the board are terrified of the increasing competition.

Management don’t know how to turn the software/services problem around with the engineers and systems they have in place, have panicked in the face of the increasingly popular Android ecosystem and have sold the farm to a predatory “partner”.

Przemo-c says:

I’e been learning qt for almost a year. preiusly i worked directly with win32 api .net and had brief encounters with wxWindows i mean wx widgets. I’m not tremendously skilled programmer but when i got the hang of it qt was great.. i mean i forced myself to using it for a week and… I fell in love with it… nice documentation simple IDE (I didn’t use advanced features of VS ) great community with samples examples and help. I liked the fact hat nokia backs QT a big company made it a strategic direction. It gave me some confidence in it’s stability and future deelopement.
Now I’m worried… i mean i developed for desktops win+linux but had an eye to using my knowledge do develop mobile apps.
I know Qt won’t just disappear… but with its future on mobiles axed… and nokia being a company that makes them…. I’m worried that I’ll (sooner rather than later) have to go to another framework… I like .net until i used Qt. Now… well i tasted something great and i wouldn’t like to go back to something well just adequate.

ps. I thing symbian with qt and revamped main ui would be a hell of a better choice than android or iOS because it’s full of features i mean my e51 was a 3g wifi router…. a gps backed bicycle computer a navigation device had t9 search thru contacts etc. for christ’s sake i had amiga emulation on it. too bad that users cling to whats shiny and new not to what works really good. As far as nokia hardware goes …. well let me put it this way technically great quality …. i won’t finish

pps. Trolltech guys than you for developing such a great framework.

kriko says:

How many of you are you prepared to switch into WP7 programing?
We allready had a presentation at out academy for WP7, MS is doing this all over the world.

qtnext says:

what you wants : Qt, Android, Objective C…. but no .net … you will lost a lot of developer Nokia, I hopes for you that there is a lot of Windows .net developer that will do software …

An oldtimer says:

I am an Finnish independent developer, started in the 1970:s writing code for the HP3000 minicomputer,

I’m a latecomer to mobile development, was thinking about starting to learn qt seriously but this caused me to look around. Seems we have a lot of vendor-specific developer environments:

– Apple iOS
– Nokia (post 11/2) WP7 (.net), S40, Symbian/QT with Meego in a very odd role
– Google Android
– Samsung bada
– RIM
– HP WebOS
– the chinese ???
– probably others

This looks like a very familiar mess: the proprietary mainframes in the 60’s and 70’s, the almost similar but incompatible unixes of the 80’s and so on.

There very little left of any of these, on the other hand emacs and gnu and C/C++ from the early 80’s are still with us and I can still use my Unix skills from the early eighties learned on a PDP-11 copy built in the Soviet Union running the then free Unix from Bell Labs 🙂

So my prediction this proprietary phone API environment will not be around for long, we will see similar commoditization as in bigger computers before, probably faster as more people know the drill.

Also since the 1980s I have learned and unlearned more MS apis than I can count (try tracing the history of MS database apis for an illustration:-)) so starting to learning more mobile .Net is not an attractive option either.

So personally investing in learning a phone vendor-specific api is something I would be doing very reluctantly, on the other hand if say QT could promise a reasonably vendor-independent stable base that could extend with vendor-specific features in a somehow controlled manner, this would be a very attractive proposition.

Of course then the structure / company behind QT should be credible for the long haul, remember all these QT license changes.

Now, could QT be used to minimize the time we developers have to bear with the proprietary APIs and can we independent developers apply pressure and otherwise work for this to happen as fast as possible (and use say QT in the meantime 🙂 ). Other approaches, WebOS Javascript-environment looks interesting ? does it work ?
Are the phone APis mature enough for commoditization to start ?

Does anyone else have similar thoughts or am I way of base on this one ?

One other thing, the Nokia change to the MS architecture in this way is a very big transfer of knowledge and money from Europe and especially Finland (10.000 layoffs in to the Nokia related cluster in Finland according to some guesses) to the US which means it may be possible to get quite important people outside Nokia to listen and help build this vendor-independent “european” ecosystem.

Reducing developer risk should also help the MS-Nokia ecosystem by helping to attract wary developers (and all those pissed off by the current situation :-))

What MS wants from this is as I understand developer lock-in (nothing new under the sun).

Steve B will have to be dragged kicking and screaming into any QT based API so a success will not come lightly. But any one remember that “Linux is a cancer” thing 🙂

Renate Meijer says:

BlaBlaBla. I wasn’t too happy with Nokia taking over TrollTech, now that Nokia is taken over by Microsoft, i guess it’s time to go looking for an alternative before this one gets “embraced and expanded” to work with M$-shit only. A leopard does not change it’s spots and managers are NEVER to be trusted.

Elviin says:

Can anybody identify/confirm this picture taken in the Mobile World Congress 2011. Is it really from the congress?

https://picasaweb.google.com/meetmeego/MobileWorldCongress2011#5573136000090017794

Kipper says:

If WP7 works on a phone then that phone runs the latest windows mobile (aka Windows CE) with directx, filesystem and device management – the works.

Windows phone OEM SDK’s allow code to be signed with the OEM’s key so they can be loaded and executed on that OEM’s hardware. No .Net need enter the picture. Only the appropriate license be given.

Qt would make an awesome toolkit to drive an alternative to WP7.

Just sayin’.

QtRoS says:

I really don’t work code with .NET
I work with .NET and Qt, and second better…

speak truth says:

Dear Mr. Elop, you will not finish in glory: you will end up in the trash.

Nokia, wake up!
Finland, wake up!
Europe, wake up!

*To* *the* *arms*, this is just plain suicide!!

Adrian Carpenter says:

Can I just say “told you so”?

http://labs.qt.nokia.com/2010/11/09/qt-4-7-1-released/

kde lurker says:

Embrace, extend, extinguish. Looking at KDE forums it seems their devs are in denial. Unfortunately, in case of Qt fork, we cannot expect them to take over development of Qt as they are mostly users of it and their plate is already overflowing with KDE.

Yves says:

Can you tell something about the future of the Qt-Mozilla port, which seems to be maintained/sponsored mostly by Nokia?

Tom says:

I guess its time to go back to GTK+ seeing as gtk+ 3 is quite nice now with out its X11isms anymore. Or maybe efl seeing as samsung (the company nokia should actually be worried about) is being used by samsungs BADA.

Seriously nokia? Your going to go up against Samsung with WP7? Qt is an awesome library. I fully planned to ditch this java-encrusted android crap for a N9 or whatever the first Meego phone was going to be from nokia. Now its questionable. Do I really invest my energy in to something some MS lackie CEO cares nothing about? Its not like Elop benefits in any way from Meego, WP7 on the other hand….

Emilio says:

The difference now the code is open, the only chance you have Qt ppl is not coming from MS, it is coming great:

1.- if you are a real big community to help each other generously.
2.- if you only one programmer like Linux Torvalds who will add Android and IOs4 “save as” capabilitys to QT.

It is funny your future, thousands of programmers, millions of customers is hanging on a single person who is so generous, and inteligent who can get deep in the Qt language and get a “easy” “SAVE AS”.

SO New-Torwalds = “save qt-comunity as android+Iphone” binaries.
Imagine you can save as your hard coded apps into Android-Iphone, and save moving.

Dave says:

Is it really black joke? http://www.msqt.org/

Emilio says:

Missing from the post before at the beginning:
the offenser is MS not Nokia,
Nokia became after 2000 an idiot, you cannot blame an IDIOT.

MS left aside many languages, pissed millions of programmers asking for moving into Studio-.Net.

Do your remember Foxpro world? same now?

300 nokians says:

..THIS IS SPARTA !!! (you now the story.. down the pit etc.)

Some finnish guy should have jumped frontstage on friday ! May be next time.. you just need 300 nokians, you know.

Long live Qt! QtCreator,QML just scared the shit out of the MS guys. So they came.. but 300 nokians will show them – rise now !

Shareholders, ehem, that must have been the scene where leanoidas goes to the oracle.

KK says:

I don’t understand why you guys hate M$ so much. Maybe It will provide Xbox Live users to Meego platform and Qt. We can have much fun and it will not change anything we like. Qt is still LGPL and Meego is still open source. So just enjoy it, why not?

David says:

Guys, why are you trying to support already dead platform for Qt? I mean, Qt is an excellent framework. I don’t know any developer who had a negative comment on it. So why don’t you open the right door, the door which has the largest development community and not platforms such as MeeGo or Symbian. Provide better support for Visual Studio, current addin is absoloutelly useless. Provide better support for apple products. You will have much larger community that way. Providing a better support for MeeGo and/or symbian than Win/Mac is an abuse for such a wonderful technology.

Just saying says:

So what’s the future of WP7? It’s a nice barebone UI for CE6 that doesn’t have any features. Who is developing CE6 or WP7? What are their roadmaps? How can the Nokia board let this happen?

Intel and AMD should find someone to produce a Meego phone so that I could buy that instead of any shit that MSNokia outputs.

D. C. Sessions says:

So all of the previous software platforms will be kep, and Nokia is just adding one more.

This solves Nokia’s fundamental “silos vs. strategy” problem … how, exactly?

georgeshu says:

I will simply interpret this as the upcoming death of Qt… We all know what happens when Microsoft goes into a “strategic alliance”. As far as licensing goes, TT has Qt as GPL then with Nokia became LGPL and now with Microsoft grinding the axe it will go proprietory… The only way forward, and the honorable thing for Nokia, is to leave TT alone to do its own thing via some other company…

QtFoundation says:

I don’t really care about the mobile market but Qt is the bread and butter for our desktop product. Qt consulting companies like KDAB, Cute Hacks, ForwardBias, FrogLogic (all of them have ex-trolls or KDE gurus) must join hands and start a Qt Foundation that can fork Qt and provide Qt support. Many customers (like me) would gladly pay for such a foundation (instead of paying Nokia today as commercial customers). And yes, I have already sent this note along to the Qt consulting companies.

Lynn Carver says:

I don’t know what to say. I don’t want another Made In China virus infected POS phone. If this is where Nokia is going, then goodbye Nokia.

Brian Duffy says:

“One thing people keep forgetting is TrollTech was a company by itself before Nokia bought it. It was living by itself and doing OK. There’s no reason they can’t go back to do the same.”

Qt was not LGPL under TrollTech. If you used the toolkit without a license from Trolltech then you had to open source your application. So they had a revenue stream from individuals and companies who could not or would not open source their applications and had to purchase a Trolltech license. What would be their revenue stream now?

Constantine says:

Might be sad that Qt wont succeed to have any significant impact to mobile world but still more and more (major) applications make use of it.
Don’t see why Nokia would like to kill it or even slow down the development.

David says:

Come on guys, MS didn’t buy nokia, at least yet 🙂 So I don’t think this deal could have any impact on Qt from MS. Anyway if MS did buy qt (I don’t think this is ever going to happen), they will provide free and open source development tools to. You have VS express, SQL Express, XNA studio express, .NET and ASP.NET MVC is open source. so what do you care of?

Finnman says:

Qt struggled under partial ownership of (and hence association with) SCO, the hated anti-Linux and Microsoft shill. Now they’re back under the yoke of Microsoft. Perhaps a spin-off can save Qt. It’s a good product and deserves and chance with a company more independent of Microsoft. After all, one of the features is platform independence. It’s perhaps time to promote that independence. Maybe Qt can be spun off or sold to another company. I hope this happens.

David says:

@Finnman
Qt is already independent from microsoft. Qt is not and as far as I know won’t be used as a development tool for WP7. I agree that platform independence is an important factor, but there is a much larger community which is targeting one commercial platform. So it’s great to have platform independence, but it would be also nice to support a better VS plugin. I can’t start development on Qt because I’m using TFS as SCM, not GIT or mercurial. And there are tons of companies/developers like me who thinks that Qt is better than MFC but they can’t start developing with it because of dumb technical limitations.

Michael says:

“One of the key benefits of joining an established ecosystem is that there is an established toolchain that everyone uses. ”

It’s quite a stretch to call Windows Phone 7 “an established ecosystem”. However, I understand that Microsoft got a great deal in their purchase of Nokia. $0!

Finnman says:

Technical limitations? I’d call them “political” or “marketing” limitations. Porting to a new platform is straightforward. Getting boxed out, ala Steve Jobs saying “no” to non approved things, may be a “technicality” but it’s not technical. If a platform goes “closed”, perhaps the small developer needs to look for an alternative. Qt helps the small developer and I hope it looks out for their best interest and hence their own best interest.

MrX says:

Another triple-E move from Microsoft; that is Embrace, Extend and Extinguish Nokia! I’ really sorry for this very successful Finish (anymore?) company that pulled so much innovation since the beginning.

Fantomas2006 says:

@An insider: can you tell us the whole story??
I’ve just read this : “Now TechCrunch Europe’s source has claimed the product is code-named the N9-01, and that it’s a touchscreen device without a physical keyboard, but with a user interface designed by “a three person external team rather than any of Nokia’s hundreds of internal designers”
Is this true ?

Marc says:

I can’t quite describe how disappointed I was by the PR event that took place on Friday – forget Meego & QT & Clutter… .
My reaction then has been to start again looking around, download HP’s WebOS SDK and in 30 minutes I had the emulator up and running – really not that bad! This is now going to be my focus during the next weeks… .
And please: stop buzzwording with “ecosystem” – cannot hear it anymore… .

Dead says:

I was planning on experimenting with QT for cross platform desktop development but that seems like a waste of time now.

Lucian Armasu says:

Are you going to officially support Android on QT?

maemo says:

on the long run only maemo will win the game.
forget meego, forget win(whatever), forget iphone, forget android.

don’t kill maemo, otherwise you will lose many customers

Guido Seifert says:

dead, you exaggerate. I agree with you that Qt for mobiles is dead, but for desktops it is still a fine choice. And will be for at least a couple of years.

Lucian Armasu, I am not Mikrokia, but I’d guess not if their new CEO can prevent it.

Relax says:

Now all Nokia’s Cute developers could releax, not responsible any more for the survival of Nokia. That could be a benifit. All this mobile-only stuff was so boring. Maybe we now see more intersting things for the desktop.

AD5XJ says:

My two cents may not be worth much given the above comments, but here goes.

For those thinking the partnership with Microsoft is a good thing for Qt or Nokia you are ignoring history. Microsoft does not have the kind of history to support such positive notions. They ARE “The BORG”. Whatever the origins, this partnership will only end up by Microsoft dominating the marketing and corporate decisions Nokia makes – if Nokia survives at all. Microsoft is not primarily a mobile wireless company. They are “The BORG”. A partnership with Microsoft means you do business as THEY decide you should. I have had first hand experience with Microsoft since OS 1.0 and Qt since 4.0. I did not just wake up yesterday.

The Nokia acquisition of Trolltech changed the focus from primarily desktop with wireless capability to primarily mobile devices and little thought to implications to the desktop environment. Even OS priorities changed from Open Source environments to Windows. This was largely due to the influence of the MS leaning notions of the new Nokia execs and narrow wireless device focus of the Company where Qt is concerned.

Nokia and Erickson got left behind in the hardware competition many years ago outside Europe. After playing catchup on the technology side, software technology did not develop to match competition. The newer software offerings of Nokia have failed to even dent the marketplace, being offered late and with serious shortcomings compared to strong competitors like Google. The upstart Windows Phone is now crowding Nokia out of the competition. That may be harsh but it is the reality. Nokia execs no doubt saw this MS/Nokia partnership as an economically beneficial thing and a way to increase market share. But they do so ignoring the voracious appetite of the leviathan Microsoft.

I am sad for Nokia/Qt employees. A year from now it will not be the same company. They will be working for Microsoft best interest and not Qt or Nokia. Even if (the unlikely even) Nokia increases market share, it does not translate to more independence and innovation.

Believe me I know how pessimistic all this sounds. But the best predictor of future behavior is past behavior. Knowing that, and seeing Nokia selling out to Microsoft does not give me the “warm and fuzzy” feeling I would like. Call me naive, call me what you will, this is not a harbinger of good things to come for Nokia or Qt.

I could be wrong – but I have history on my side.

As a Qt developer of Open Source applications, I am now looking for alternatives even though I am still a Qt Ambassador. The sad fact is Nokia will be assimilated. They will not be a independent European company any more. Nor will Qt be the Open Source standard for cross-platform programming tools – for any hardware platform. At best (and I do mean BEST) Qt will be assimilated into MSVS for Windows products ONLY in the end. This is the history that has repeated over and over. There is no reason to believe anything will happen any different in the future of Nokia.

It is sad – really!

Debianero says:

I do love Nokia phones but ain’t going to use Winblows never ever.

Nokia, if you want to keep me as a happy client, keep away from Redmond virus.

qtnext says:

just show that : http://conversations.nokia.com/2011/02/12/what-is-the-future-of-qt/#disqus_thread

I love the translation of what is said …
I hopes that Qt is no dead,… but ….

Guido Seifert says:

Relax, I doubt they can relax. Actually I expect some serious job cuts under the Qt developers real soon. As I see it, the most severe disadvantage of Linux compared to Windows is the by far smaller choice of high quality commercial software. Qt allows without much effort to develop hight quality programs for Windows, Linux, Mac and a few other systems using the same code base. This is potentially highly disruptive for Microsoft. And we are dealing here with Microsoft. For all it’s worth Nokia does not exist anymore. And Microsoft was never known for fairness against competitors. So I hope I am wrong, but when I look into my crystal ball I see a minimum Qt team, which is just big enough to create the absolute minimum updates, which are required to prevent Qt falling under the BDS license.

Emilio says:

Imagine you can “save as” your hard coded apps into Android&Iphone.

WP7 will have a very hard time to survive, WP7 needs MORE you, but you do not need REALLY WP7, so let WP7 chase you with clean tricks, not closing QT. (It is something dirty closing QT support to get more devs for M$studio.
Devs, You are the jewell of the crown, nowadays by Internet.
BAllmer means they give great addons for nokia: “Bing,Office, XPlive” I prefer Google, OpenOffice, and XP_oldVers:
(http://www.youtube.com/watch?feature=player_embedded&v=xe3ksR8zgXg)

John Doe says:

“But… but, OVI is ALREADY one of the largest app markets on the planet. And your point was…?”

Sorry to mention this, good sir, but you have obviously mistaken “app markets” for “failures.” These phrases bear remote resemblance to each other, so I believe it was unintentional.

marcovella says:

Ok. Allow me to give you a good idea. The idea is this: a smartphone with a static IP address and a small (fast) internal server with all the “services ” that we would have in the “cloud” (docs, calendar, business applications, etc.). For those who do not believe and have faith in the “cloud”. For those who want to access documents from any desktop but do not want to entrust their secrets to Google, Microsoft or other … For those who need online services very personalized. In short, a different idea of “cloud” and Saas. Qt could be the ideal platform for the development of this idea. If you are interested, you have my email … Bye

Guido Seifert says:

marcovella: The idea is this: a smartphone with a static IP address…

Nice idea. Come back when IPv6 is widely available. 😉

Call as Wuo says:

Hold your horses! Its not over until the fat lady sings!

Nothing is everlasting, including company strategies.

Here in Finland it has been wondered why Mr Elop announced the incoming death of Symbian/Qt platform in the way he did, hurting the QT developer adoption and sales of Nokia’s current products. Mr Elop certainly has a lot of explaining to do, at least for Nokia staff and for the investors in the soon coming general meeting.

This MS marriage is a HUGE risk for Nokia and nothing guarantees that Nokia Windows phones will be successful.

There is no way Nokia will initiate the factual Symbian/QT platform close down until this MS marriage is proven successful.

It is obvious that this strategy alignment will divide Nokia SW engineers to 2 camps, the ones working for WP7 adoption and the ones working for Symbian/QT products.

Hopefully this spirits up the Symbian/QT Nokians to work even harder. “Let’s show them how much faster our UI is! Let’s show them how we can do the same with lesser HW requirements” etc.

So, dear QT developers, now it’s not a time to discard this wonderful development platform we have. Instead, let’s show Mr Elop how broad the developer support for QT is. Let’s show mr Elop how fast QT apps can be developed. Let’s show Mr Elop what QT is capable of.

jack jia says:

Qt works on Windows platform right now. Qt is beyond Nokia and it won’t die because of Nokia or Microsoft or any other companies. Nobody can throw Qt under any buses… you guys are kidding.

Sander van der Wal says:

Qt is not an option anymore for mobile development, except for projects where you already have a Qt codebase, or for projects where the life expectancy of the app is less than the life expectancy of Symbian.

Qt is now also in trouble on the desktop. It main sponsor is abandoning software development, because they were so bad at it it almost sunk the company. In a proper business (and Nokia is still a proper business) you would sell nonessential assets, and Qt becomes nonessential in the next two years.

There is now a new issue. I suspect that Noka would rather have choosen to support Qt on WinPhone7 too, to prevent this PR disaster with their screwed developers. But they did not choose to port Qt. This is an indication where power lies in the Nokia-Microsoft relation.

hsm13 says:

PEOPLE DEMAND REMOVAL OF ELOP

PEOPLE DEMAND REMOVAL OF ELOP

PEOPLE DEMAND REMOVAL OF ELOP

Mika Hanhijärvi says:

@Joh Doe

> Sorry to mention this, good sir, but you have obviously mistaken “app
> markets” for “failures.” These phrases bear remote resemblance to
> each other, so I believe it was unintentional.

That’s not true. Latest numbers tell that before friday there was more than 4 million downloads / day in Nokia’s Ovi Store and number of downloads per day was growing really fast.

Whitoput this idiotic WP7 decision I would not have been surprised if Ovi Store would have reached 10 million downloads per day before end of this year. But now it will never happen…

There is also lots of good applications in Ovi Store and number of good apps and games were growing.

Ovi Stiore sure is niot failure, far from it. But now Nokia is destroying everything…

Anton says:

I am nohest,

I didn’t read all comments already posted.

I can tell you one thing how I understand this announcement:

– Windows Phone is now the “primary platform”
– this means the other platforms will be discontinued
one day
– this means: every day I continue to develop for such a
(probably) discontinued platform, I am wasting time and money.

Thats all … no, wait: Its not a good sign if a company changes
their strategy too often (remember Borland..).

Anyway: if supporting two platforms like symbian/MeeGo
is too much for you, how will you support three platforms??

Look at Apple and MS, they do not support n platforms..

Thats it.
Much luck 😉

vlt says:

It is curious that the head of Symbian, Jo Harlow is located in Britain, when the core of all Symbian is in Finland. In addition with the adoption of Microsoft (USA company) all seems to indicate that bussiness will be closed in Finland and nordic countries and the new needed bussiness will be moved somewhere else, perhaps to USA and UK where is good for Microsoft.

finnman says:

1) Qt is a good product.
2) Microsoft’s takeover of Nokia is bad news for Qt.
3) It’s going to be hard to spin this as “good news” or “dont worry, be happy”.

The absolute best thing to keep customers happy is to recast Qt as an independent company: split if off, take some cash for whatever value investors think it’s worth and have the new investors install a board of directors.

I’d am real reluctant to totally commit to using Qt on a new project until the clouds clear. Sure, I’d code it to plug the Qt interface on top of it, but I’d hedge my bets on making sure it can plug into other interfaces.

My 5 cents.
As an iPhone and Android game developer I can say the following. Lack of native support on Windows 7 will kill WM7 for me as a potential platform.
We do not have ability to rewrite all our games on .NET, because budgets for such porting will be high. At the opposite side we have at least 10 AAA casual titles we can deliver to Windows Phone 7. The same situation was on Android at launch, but after 6 months passed they’ve reconsidered their decision, because in every ecosystem the main question is developers.

So what do we have now, all platforms with big number of devices sold have C++ native development. Development budgets on C# will be the same as development for Android & iPhone and it no make any sense because number of WP7 devices is very low.

As result WM7 will have less good games and less good applications. Especially because small companies just can’t afford porting to WP7.

I wish Microsoft & Nokia good luck 🙂 They’ve lost all battles on mobile market during last years – and WP7 with current strategy will fail also.
I do not count Symbian, because it’s already dead for a long time.

I like Nokia, and I’ve developed lots of games on S40 and S60 devices, but I do not see perspectives even with new direction with Microsoft. Seems they forgot main thing that very important role in platform ecosystem is developers.
Microsoft lost the war with Silverlight on web-market, and now they’ve decided let’s put dead platform to mobile phones. XNA was published initially as a method for indie developers to do something for XBox. Big developers always had native development kits. I think it’s not a good approach for the mobile.
I think my thoughts is clear…

Marc says:

Hehe… too cool when at today’s Nokia press conference at the MWC somebody asked Mr. Elop “Are you a Trojan Horse?”
:o))
Here the story:
http://www.liveside.net/2011/02/13/nokia-press-briefing-at-mwc-elop-will-be-much-happier-with-a-nokia-windows-phone-in-2011/

Jhill says:

@Vitaliy,

You can use Mono on Android and iPhone, allowing you to reuse C# across all 3 platforms

Alex says:

So Qt won’t be ported to the highest phones in the Nokia range meaning Qt developers are excluded from writing for the flagship Nokia phones? (Or perhaps that’s flagship Microsoft phones branded as Nokia…)

That just makes me think why bother then with Qt in that sector? Pointless, you can’t (won’t be able to) write for iOS, Android or Nokia smart phones with it. As I won’t touch a Microsoft product, nor Apple and I’m not so keen on Android if or when my N900 gives up I’ve no idea where to go and take the things I’ve written for it.

No this isn’t happy news at all for Qt.

Ancient c0der says:

Call as Wuo has a good point. keeping Symbian afloat with innovative 3rd party QT applications starting tomorrow seems to me a good way of showing off both QT and the usefulness of a motivated developer community in a way to make the board listen. If it fails, QT is still open source so it can perhaps be made to go somewhere else.

Even if the revival does not work so can Symbian be a good place for small nimble companies now when all self-respecting powerpoint people most likely will declare it a dead end.

Actually the N8 owners I know seems to like the thing, they were not happy with 11/2.

And we Finns have some national interests in this I think 🙂 It may help.

What’s the best (most cost-effective developer phone) phone to start with. C6, C7 ?.

I’m an independent third party developer not affiliated with Nokia in any way, but i own an N900 and a 770

@Jhill

Technically yes, we can, but only for new titles. The problem that we have big codebase on C/C++. Everything was written during last 10 years and it no make sense to rewrite this code. C/C++ is de-facto standard for all platforms. I like C#, but C/C++ should stay. It’s much easier to drop the platform for now. If Microsoft will beat everyone on mobile market we’ll start thinking about porting.
We have an SDK that works on PC / Mac / Android / iOS with OpenGL / DirectX renderer, lot’s of cool features for games… and only one choice is rewrite everything to C#. 🙂 We can rewrite SDK, but it’ll require to rewrite all games we’ve made… it do not make any sense for us. They just wasting our time, and actually it no make sense for us to enter the same water again.

We want to produce new high quality games with all our partners, and we do not want to waste our life on rewriting the games on different languages. The funniest that everyone except Microsoft will have C/C++. Our games can be easily adopted for Nintendo 3DS, PSP2… even XBox… what do they do? They slowing themselves. They can get hundreds of high-quality titles from many big & small companies… We just need one thing NATIVE SDK. 🙂

Qt also can be easily ported, again native SDK…
Sad story…

serkol says:

@Call as Wuo
> So, dear QT developers, now it’s not a time to discard this wonderful development platform we have.

Right, Nokia-employed Qr developers, work harder, until Mr. Elop fires you. Qt will not be ported to WP7 so that Mr. Elop can greatly reduce the R&D spending (e.i. initially reduce the meeGo and Qt departments, then eliminate them altogether)

Cool outside Qt developers, work harder on your mobile Qt apps, and keep telling your wives and kids stories about the great future. Oh, if you don’t have wives and kids, you can tell these stories to your parents, when you ask them for more money.

Mr. Call as Wuo, do you think you are talking to idiots?
/rant off

Bart says:

A good development library is essential for a certain platform. In this case Qt is gold for Linux and it has the massive advantage of being cross platform and is used by a lot of companies. It only gained popularity when being bought by Nokia to spread its abilities to the mobile platforms too. Which is absolutely what MS doesn’t want! With this deal, MS saw the chance to acquire a big player on the mobile market and decreasing the focus on Symbian and Meego with the consequence of decreasing the popularity of Qt and lessen the number of competitors over time (Symbian will remain for cheap phones, Meego will be forgotten). Whatever Nokia says, if the Win7 Phone platform will be a success, the development of Qt will not be as important as it had been when this deal hadn’t been made. This is not only a hit for Meego or Qt, also a bit for Linux as it could have been a major player on the mobile market (smartphones and tablets).

LinuxGuy says:

So let me see if I understand correctly….
…what’s in jeopardy here is Commercial Qt …right? In other words Microsoft could reasonably be expected to move toward sabotaging cross-platform Commercial Qt right? They would not be able to kill LGPL Qt -which could be forked at any time- but they could reasonably be expected to move to kill Commercial cross-platform Qt …Correct?

qtnext says:

Yes … there is some true news about what’s happen ….
http://blogs.lesechos.fr/mobile-world-congress-2011/stephen-elop-fait-son-show-mais-n-a-rien-a-montrer-a5115.html

in short :
– Elop has nothing to show (samsung in another room … show tablet …)
– it’s not sure that Nokia show a winphone in 2011 … the problem of meego was that it was slow to come…
– nothing is really clear
– What’s about Qt…
– the internet debat about Elop action in Microsoft …

Tom says:

Elop: “Question is, will Nokia put Qt on Windows Phone? Our initial response is no, that’s not the plan. The reason is that if we encourage a fork in Windows Phone’s development platform, we could create a situation where we confuse developers and consumers.”

1.) Why the hell should this confuse consumers? There is no difference for them.
2.) “it confuses developers”: So choice is bad? Does he think developers are idiots and get confused by two toolchains? WTF?

It’s obvious that Microsoft doesn’t want Qt, that’s the only reason for this stupid move.

PDBL says:

Do you really think microsoft phone manufacturer division ( before known as nokia) will be allowed to developp something allowing interoperability and portability?
qt and linux are communism in the religion of your CEO

pdbl says:

novell had the same kiss of death a few years ago…

CowardNokiaBendsOverForM$GangBang says:

KDE should fork and name the new project BQT, from Brave QT, not cowardly Nokia QT, or Brokenheart QT :D, or Better QT, or Be cute something like Google’s Don’t be evil etc

Shame shame shame on Nokia. I didn’t feel that brokenhearted since highschool

Jan says:

After all these depressive comments something more positive:

WebOS 2 (Palm Pre) from HP already ships Qt 4.6:
http://opensource.palm.com/2.0.0/index.html

There is an Android port of Qt including QtCreator integration:
http://code.google.com/p/android-lighthouse/

An Qt port for iPhone is under development:
http://www.qt-iphone.com/Introduction.html

Frank says:

After all these depressive comments something more positive:

WebOS 2 (Palm Pre) from HP already ships Qt 4.6:
http://opensource.palm.com/2.0.0/index.html

There is an Android port of Qt including QtCreator integration:
http://code.google.com/p/android-lighthouse/

An Qt port for iPhone is under development:
http://www.qt-iphone.com/Introduction.html

So I don’t think Qt is dead

TechnologicalSingularity says:

* No native C++ development = no talented developers = no valuable applications.
* Either Nokia-MS offers Qt/native C++ for WP7 or WP7 and Nokia die, this is as simple as that.

* Also, as you might know WP7 is already a dead platform. It has already been announced by Intel that Windows 8 will run on Intel-powered tablets and smartphones with an extra GUI layer adapted for these form factors. In a about one year and a half, you will be able to run your native C++ applications on Windows 8 desktops, tablets and smartphones. When this happens the WP7/.Net/C# app market will completely evaporate (it’s already vaporware anyway).
So why spending time on migrating your native C++ code base to slow-lame C# just to be able to run your apps for 1.5 year on a stillborn platform that won’t reach 5% of the market before it’s killed off ? Your best move is to stick to C++, wait a bit and run your code as is on Windows 8 smartphones.
Forget about WP7 and Nokia, these 2 platforms/brands are already completely irrelevant.

PP says:

Not porting Qt to WP7 clearly isn’t a decision that’s going to find favour with this audience, but I can understand it and sympathise with it technically. Official support for Qt, or more specifically Qt’s emulation of WP7 look & feel along with any WP7-specific integration APIs (live tiles, etc), would be a real millstone around their necks.

If the S60 Qt UI experience is anything to go by, it will take far too long to develop a WP7 theme to production levels of quality and faithful reproduction; significantly longer that it should really take Nokia to ship their first WP7 devices (if they make sensible component choices anyway). Assuming a Qt WP7 theme does catch up temporarily, what then? You expect the MS UI team to work in lockstep with Qt engineers forever more and slow down their forward momentum? Doubtful. You expect Nokia to unilaterally hold back their own devices until Qt is ready each time? Suicide. Or maybe it’s just fine for Qt apps to look a little bit crappy and out of place for a few months after some major WP7 release cycles.

Qt apps on S60 are a little bit incongruous but arguably add value. Qt apps on Symbian + Orbit would’ve made sense, with Qt being the master UI framework. Same goes for MeeGo. But WP7 has a high quality UI with some very strong visual metaphors at work, unfortunately with frameworks written in a technology that it’s always going to be awkward for a Qt back-end to leverage.

At best, Qt on the phone ends up reduced to the same status as Qt on the Mac and Windows desktop; useful but an outsider framework that’s always playing catchup. At worst, the effort required and the technical barriers to development and distribution in mobile mean a port never gets taken beyond the relatively cheap win of running the usual set of graphics demos that don’t need to reference the native frameworks in any meaningful way.

minotauros says:

a few years back when TT got acquired by Nokia a friend told me he will drop Qt eventually coz LGPL was put forth… guess what? I am considering to drop qt as well… not long to go now…

Martin says:

Remarkable.

First, the dream of selling another 150m phones could have been real if Nokia didn’t so publicly say they are dumping Symbian. Who’ll buy a phone that’s known to be EOL? Who’ll write apps for phones that are DOA? So, forget Qt on Symbian full stop.

One phone per year for a platform like meego won’t attract either consumers or developers. It will have a small market and fizzle out. Forget about meego as well.

Most interestingly, “Qt everywhere” says you, but not on WP7? Well, this one is a real cracker.

LOVE_MOSS_NOT says:

Let’s welcome the new overlords MICROSOFT. Let’s just learn C# and Silverlight, the future of the web 😉

Valdemar Kjaer says:

It’s sad to know that Nokia will use Windows Phone 7. I would prefer to work with Android.

serkol says:

My final 2¢, and I really stop reading and posting here 🙂

– Nokia’s MeeGo/Qt teams failed. They were too slow. Why? Mismanagement, lack of motivation, lack of talent, proverbial Scandinavian slowness? I hope because of mismanagement, but who knows…

– I never cared about Qt Mobile a lot, now I will never care about it at all.

– I had big hopes for Qt desktop. I spent the last 8 months writing a Qt Win/Mac app. Now I’m close to regretting my choice, but I will have to stick to it for some time…

Why I have my doubts about Qt for desktop? See #1 – Qt team failed in their primary task (since Nokia got TT). Are these people capable of fast and high-quality development, that is needed to fix desktop Qt, and then to constantly keep pace with Win & Mac? Now I doubt this…

If Intel takes over Qt, there’s a danger that they will only care about MeeGO. Well, if they are wise, they will understand that currently Qt can attract developers ONLY if it is a high quality desktop cross-platform tool that targets Win & Mac, where the devs can make money now. But Nokia did not understand that, they ignored the desktop part of Qt. Will Intel (or whoever takes over Qt) get this? We will see soon…

Jonas says:

Is this anything but Nokia executives panicking over loosing the smartphone marked, and now turning to the strategy that no-one ever got fire for: Microsoft.

That said, and implied that I’m not afraid this will kill Qt… I would still like to know what Nokias business plan for Qt on the desktop is ?
I see you’re selling support and licenses, but is that a viable business plan…
As developer I would be more likely to invest in Qt if I knew there was a business plan…

Cynic says:

@jonas your question may be rhetorical, but if you got the business plan, would you believe it? Last October this new Nokia CEO and management team said were fully behind Qt. Now, just 4 months later and it does not align with the long term company strategy. Why would you believe anything they say?

Toledo says:

You guys make me laugh !
You should stop trusting false standards which are being owned by big companies like Java/Oracle, Qt/Nokia, .Net/MS, etc… because there are only 2 outcomes when you adopt them :
1) They fail and you fail with them.
2) They succeed and then these companies will cash in on your back.

I guess wxWidgets get a well deserved revenge here…
Hopefully with what has happened to Qt, wxWidgets will get even more followers and will support even more platforms than it already does.

Bye bye Nokia and bye bye Qt !

HarHar says:

And end of this year Nokia will switch from WP7 to Android and Java is the new way then. Half a year later it’s maybe Clutter, then WxWidgets, EFL, etc. So, hopefully it switches back to Qt in ~3-4 years.

toran says:

Article from Computerworld (found on digg.com):

Peter Winston says:

Qt has a bright future.

Qt is just as good today, as it was last week. There are a ton of companies, and developers using it. – that didn’t change.

Yes, this is a loss. and it will hurt or even a kill Qt/Meego phone.
But Meego is more then a phone, and Qt is more then Meego.

Nokia is a big company. They can handle more then one project at the same time. If they say they are going to continue support for Qt, I believe them. At least, I will give them the time to prove it.

ilmirajat says:

@int19h: Thanks for explaining why you cannot just compile Qt to WP7. I found your explanation very interesting. I haven’t yet studied much how to develop software on WP7 and my CLI studies are in progress. I have to admit that I didn’t know that you cannot run unmanaged code on Windows mobile.

**

Even if I know practically nothing on coding with Qt, I want to comment one thing: I doubt if Microsoft sees Qt as competitor to .NET framework based mobile frameworks (XNA and Silverlight in case of WP7).

I don’t believe that “It’s obvious that Microsoft doesn’t want Qt”. It might be so, but it is not obvious. I don’t think that Microsoft want to “protect” .NET from Qt. Rather the question is how much would it cost (time, money and architectural trade-offs) to fully support Qt on WP7. Financially it makes no sense to exclude any technology that potentially would increase significantly sales of licenses and services without a very good reason. Pride of “our own technology” is not such reason.

Microsoft gets highest profits from software licenses and services. Software frameworks, compilers etc. are not that good business – at least, not directly. Currently *all* CLI-based (Common Language Infrastructure; core infrastructure behind .NET framework) compilers/interpreters are free – this includes C#, F#, VB.NET, (Iron)Python, (Iron)Ruby and PowerShell to mention only those languages, I have used… NET-framework is free as well and there are free editions of Visual Studio and SQL Server. In general, Microsoft emphasizes that they want to let developers to use the language and the framework he/she finds best/most convenient.

Another question is, how much it would cost to make Qt fully WP7 compatible and how much it would take time? (I really like to hear some estimates.) Even if Qt was better framework for mobile games than XNA and Silverlight together, would it be /so/ much better that Nokia (and Microsoft) should invest in porting it to WP7 /right now/? Notice: It’s not only about money and time. E.g. Windows security stuff rely heavily on CAS (code access security) and unmanaged code don’t listen it at all. If I have understood right, supporting Qt on WP7 would imply some security related architectural trade-offs that does not apply to XNA or Silverlight.

Rudy says:

@Toledo: Perhaps you have never use wxWidgets before. If you are going to use it, Congratulation. And I believe you will regret your decision soon. So many bugs on wxWidgets. Have tried it once, before Qt and now I never looked back. wxWidget is a very sensitive platform, it will crash most of the time as the underlying code is not tolerant for any fault.

Hope Qt will survive this storm and continue its development….

Alex Nguyen says:

why are you trying to juggle so much at this point in time? this decision is not only causing your consumers confusion in choosing a solid product, but it is also straining your developer community.

don’t be square. you’re gambling in the wrong way.

Toledo says:

@Rudy: Stop “trolling”… wxWidgets is a great C++ GUI toolkit, very intuitive, with blazing execution speed, truly native (not painted stuff a-la-Swing), very stable and best of all : truly free and open software. I can understand why you and most people on this forum are pissed off of having made the wrong choice but no need to bash other products. There are great alternatives to Qt around and wxWidgets is certainly one to consider very seriously.
Anyway I wish you to enjoy your new Qt-M$ development environment ! With the recent Java-Oracle debacle it’s another hard-earned lessons for people who chose proprietary technologies.

Toledo says:

The perfect new branding and marketing for Qt within the new M$-Nokia “ecosystem” has just come up to my mind :

M$-DNA-Qt.Net disintegrated development environment

LOL !

NuShrike says:

@ilmirajat Let’s try to explain it simpler since you’re not getting it.

Square peg, no hole.

Alex R says:

Nokia – Conning People

finnman says:

There’s no reason for Nokia to hold on to Qt. It’s still valuable property. Sell it for what the market thinks it’s worth. Spin it off. The Qt team needs to go to the CEO and tell him to spin it off. Buy some company that’s about to go bankrupt for chump change, sell Qt to this newly renamed “Qt Corporation” company for stock and say that they will sell off 10% every 6 months for 5 years and will not be involved with the new Qt Corporation board of directors.

evan11 says:

Have just spent more than a year developing a Qt application that is almost ready for release in the ovi store to hear this great news. So my application won’t be available on nokia’s high end phones because Nokia has now a different toolkit! Bloody great! Colleagues said that I should target android, but I’ve been using Qt for more than 10 years and looked like a sure thing with Nokia’s backing, unfortunately looks like they were right.
Now to help out with the android port and hopefully google sees a new opportunity and throws some developers at the android Qt lighthouse port.

GreyGeek says:

@int19h:
You haven’t used Qt, have you? I say that to give you the benefit of the doubt, otherwise your implication that C++ is “memory-unsafe” Qt is memory-unsafe is a blatant lie. Check the Qt API for Q_OBJECT at http://doc.qt.nokia.com/latest/qobject.html#details and learn how it eliminates memory problems with C++ pointers, garbage collection, etc.

When you extoll the virtues of .NET/C# be sure to explain why .NET collapsed the London Stock Exchange for an entire day, costing them hundreds of millions of dollars, and why the .NET trading program didn’t come even close to the transaction performance figures Microsoft claimed it would reach. Also, while you are at it, reflect on Microsoft’s “Highly Reliable Times” ad which was composed entirely of disinformation. Then there was the Chinese Olympics fiasco when SilverLight barfed a blue screen on the ceiling of the Bird Pavilion, for all the world to see. Nokia should consider that when they start seeing BSOD’s on their Nokia WP7 phones.

ctc says:

Just can’t see why Nokia will not continue his promise of QT everywhere.
Nokia loses.

andres says:

We would have loved to develop some cool apps for Windows Mobile 7 using Qt. But now with Qt not being available there we won’t be able to do so. We just do not have the manpower or money to invest in a platform whose success is far from certain. With Qt it wouldn’t have been difficult, the learning curve would have been minimal. Instead we are likely to bet on Android for our smartphone activities. I can imagine that there are a lot of developers in a similar situation.

Amir says:

Instead of unifying its devices Nokia is fragmenting it more. It seems Elop does not understand basic of Mobile industry. Why he don’t put effort in Meego and make it best smart phone user experience. With the help of Trolls I am sure it can be done. No matter its getting late if it is good it will be hit.

And from WP7 I don’t think Nokia will get any benefit because.
– WP7 is still trying to get its space
– Developer community is not that much good
– Meego is better than WP7 because it has Qt developer community and once a good device comes the OviStore will be crowded by so many cool apps and will create the ecosystem.

Even if WP7 on Nokia becomes a hit here is how Nokia will loose.
– It will just become a OEM company.
– Nokia will loose the space to innovate.
– All effort in Qt and Meego will be lost.
– Distraction of developers from Qt and Meego will be harmful for Nokia Tablets strategy (if any)

kde lurker says:

This is a strategic move by Microsoft to eventually acquire Nokia. Why?

1. Nokia is the largest mobile phone manufacturer
2. Nokia has a huge IP portfolio
3. Qt is gaining traction among developers and it is a direct competitor to Microsoft development tools

I cannot see Qt sold to someone else. Once Microsoft get their hands on it they will bleed it slowly to death.

janne says:

Lots of nonsense here, high pitch fearmongering etc.

The fact is that Nokia was in a really bad position, especially in the brand building high end segment. Symbian is becoming old and tired, and the MeeGo is not ready for mainstream yet.

Selecting WP7 for the main smartphone strategy was the right choice IMHO. .Net 4 with WPF is a great dev platform. As a Qt dev, I feel for you guys. But I’m also certain that Nokia will continue developing MeeGo for smart phones, It makes no sense to tie a future of a company to the will of another company without a backup strategy.

bill gates says:

Elop is an arsonist or better yet, an economic hitman.

SymbioliQt says:

Money, customers are not important. Creativity is all. A company without creativity is nothing.
Previously, you could say ‘Nokia is developing phones’. Now, with the almost killing of the dev part, we have to say ‘Nokia is eloping phones’.
This new verb ‘to elop’ means : to produce without creativity. A sure path to failure IMHO.

ex-QtDeveloper says:

Bye bye Nokia, Bye bye Qt 🙁
Nokia+symbian OK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Nokia+MeeGo OOOKKK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Nokia+windows NNNNNOOOO!!!!!!!!!!!!!!!!!!!!!

QtLessNokia says:

What about the Qt-Team to leave Nokia reanimate Trolltech with support of e.g. Intel and other 3rdParties and leave the sinking Mobil-Ship M$ and Nokia, which are joining each other to sink faster.

Gordon Freeman says:

janne:
>.Net 4 with WPF is a great dev platform.

Okay, now try saying that with a straight face. I experimented with WPF before using Qt, and I’m sorry but WPF blows. Moreso now that Qt Quick has come along. XAML is comparable to Qt’s QML, and QML is orders of magnitude better, and far, far less verbose.

What we really need here is for a Troll to give us assurance that Qt on the desktop will be commercially developed and supported into the future, well after Nokia has forgotten about Symbian and MeeGo. If we can’t have that assurance then unfortunately it’s time to look at something other than Qt for future projects.

Montesir says:

Please, clarify to me:
Will nokia continue to support Qt for desktop platforms or not?
What happend to Qt creator 2.1 version which was supposed to be released through December 2010, but what I see its still at beta version in spite of two months later from the exact date of release.
Frankly, I am afraid that this may be an indicator that Nokia is no longer interested to Qt. Confirmation needed, pls.

D says:

This is clearly very bad news for Qt and am really concerned about our investments in the Qt framework.
I’m sure that the Qt Team at Nokia has a hard time as well and information is very sparse but I would find it most important to get some “official” feedback from Qt on what to expect.
Thank you!

Andreas says:

Hi all,

there is no future for Nokia and Qt together, because there is no economical reason that Nokia invest in a framework (and the developers), which doesnt support some of Nokia phone OS (Symbian will fade out, Win7mob will be even for low end).
There is still Qt future for huge OS (PC OS: mac/unix/linux/win7)
maybe and hopefully Nokia will sell Qt or it goes back to trolltech.

Andreas

Guido Seifert says:

> What we really need here is for a Troll to
> give us assurance that Qt on the desktop will
> be commercially developed and supported into
> the future, well after Nokia has forgotten about
> Symbian and MeeGo.

Would you really believe them? Nope, I don’t want to imply that they are liars, just that they are lied to, too. The Nokia decision might be bad for us developers, but for the Trolls…. 🙁

Thorbjørn says:

I agree, Andreas
In the future Qt has nothing to do with mobiles Nokias mobiles. This blog is a non-answer from a director just hoping the best for the future.

The key point problem is point 5 in here.
http://www.liveside.net/2011/02/11/the-top-10-bullet-points-on-microsoft-nokia/

This burns the bridges and leaves Qt in close to nowhere. When Nokia won’t eat own dog food, what kind of position does it put Qt in?

The funny thing is that this is highly logical for the current director to do this. If he had went on with MeeGo and Qt it could be a great success, but if it did not go as well as hoped – it would be fail for him personality.

Now he ensures that he can return to a good MS-position if this probably more risky operation fails. (He should never have been hired.)

Trojan says:

I really hope the Finnish regulatory authorities investigate Elop’s “deal” with Ballmer. It’s so blatantly one-sided, this just looks a bit too much like a ploy to liquidate a company to the benefit of another rather than a genuine business deal. For companies like Samsung, HTC, etc… WP7 is just one (insignificant) OS amongst others. Why did Nokia feel compelled to tie its survival to the faltering WP7 platform ? Nokia is too important to Finland’s economy for it to be let killed so easily.

Guido Seifert says:

> Why did Nokia feel compelled to tie its survival to
> the faltering WP7 platform ?

IMHO this is not the problem. The problem is the decision against Qt. With ‘Code Once, Deploy Everywhere’ we all could live with WP7. Maybe this thread would be full with mockery, but never with such strong pessimism.

I saw other companies fall into Microsoft’s tentacles. No one survived 10 years after… Borland (old time ago), Novell(not so long), I am sure there are many other similar cases. The painful of this is that Nokia HAD A BRIGHT FUTURE WITH QT AND MEEGO (look the Android case). Now we will all go to Android’is Java platform. Pity for that. I loved Qt since 2004. Our company’s 8 developer staff live from Qt. Now will need to change direction. American CEO, don’t like you. You are like all them: oracle’s CEO, Microsoft’s CEO, like to make us hate you because you ruin in what we believe. Good dollar’s business in the long term, another buried company afterwards.

momesana says:

Nokia made a bad decision by dropping Meego. This deal benefits nobody but microsoft. That’s the second time Nokia stabs us in the back. The first time they did so was when they dropped Qt Jambi and now they are going to effectively kill Qt. We should seriously consider forking Qt.

soulcheck says:

@qtnext
WP7 developers obviously are 😉

tzeth says:

My company have just suspended Qt Mobile development all developers are supposed to transfer to Android.

momesana says:

Take a look at that page: http://www.dailyfinance.com/company/microsoft-corporation/msft/nas/institutional-ownership

Elop is ranked 8. amongst the “Top 10 Other Holders” of Microsoft Shares.

Guy says:

If you ask me some (US) investors are pulling the plug from Nokia now, and they are heavily hedging their losses with MS stocks and propably some direct competitors(Google, Samsung).

They came to the conclusion that this is the only option to rescue their investment, since Nokia is performaing so bad.

Andreas says:

Hi all,

so now we have to forget thinking about Nokia. For me as a developer there are some questions for Qt as cross platform API for the next years.

Are there possibilities for Nokia to kill, destroy Qt somehow?

Is there a future for Qt on phone and pad operating systems?

Is there a future for Qt for classic PC operating systems?

Zeb says:

Being a desktop developer I’ve really welcomed the impact Nokia have had on Qt, namely LGPL and PySide – I can do my own stuff and not worry about licensing. Of course I’ve had various employers dating back to TrollTech days who’ve paid for the commercial licences.

Generally I’ve owned Nokia phones and last year I was going to buy a Symbian smart phone to develop on but couldn’t justify the cost compared to an Android one. Maybe now I’ll finally get around to learning Java.

Hopefully Nokia’s performance is just “regression to mean” and will continue to release quality products in the future. If not then it’s been nice knowing you.

David says:

If there is no Qt for WP7, than push the desktop segment please. Go for Windows/Mac/Linux. The most part of devs are desktop developers. Don’t kill Qt

Marcus says:

I was on denial trying to beleive the switch to WP7 was not going to come true, but now all hopes are gone. It took me a long time to convince people at work to start developing with Qt Creator. I made some demo applications, showed that they could work at Nokia mobile smartphones, windows and linux without many changes. It has been a 1,5 year process, and now this frozen water shower send all my arguments down the drain.
I was about to buy the N8 but know I will wait the death of my E71 and see what will happen in the future.

AncientCoder says:

This might be a blessing in disguise and a real opportunity for Qt to be adopted as the de-facto development tool for Android and iOS. I don’t give a fig about the hardware. In fact this is half the problem for Qt it’s destiny should not be controlled by a company that owns the hardware.

Best thing now is for somebody who understands what Qt is all about to come in and pluck our baby from the burning platform. 🙂

JubiluM says:

“… and Microsoft’s tools would be used for Nokia Windows Phone application development …”

Yep. But there is a slight problem if you look at it from a Qt-developers’ viewpoint. Namely…no one, ever, under any circumstances wants to touch crappy MS tools or their bitchy API’s after having the joy to work with Qt.

Bottom line….your sincere Qt-community will not follow you to WP7. Good luck all the way down.

Tom says:

I hoped for a string showing of Intels MeeGo use, unfortunately it wasn’t: http://www.engadget.com/2011/02/14/intel-shows-off-more-of-its-meego-tablet-ui-still-needs-lots-of/

Samuele says:

Microsoft is like a cancer, initially start as one small piece, but after that it become big enought to kill you.
Personally after 10 years of Nokia phone and also as qt developer (in my spare time) I do not want to buy another Nokia phone for rest of my life.

David says:

@Samuele
I’m quite happy to be MS dev for ~10 years. I’m happy with nokia’s decision to bring WP7 to their phone devices. I’ll be happy if Qt continues to evolve and provide better support for desktops/platforms and mobile platforms. The cancer is in your brain friend

Harry says:

Union already wants 100.000€ (135000$) for every fired worker… now really?!

http://www.reuters.com/article/2011/02/14/us-nokia-jobs-idUSTRE71D2MH20110214

A student, a developer, a shareholder says:

Honestly, you got to push the managers to allow and announce a Windows Phone port of Qt as fast as possible. A lot of damage has been caused already, but it’s not too late!

WHY?
(1) Windows Phone Developer Tools only support Windows Vista and Windows 7 as a developer platform. There are a lot of institutions, companies and individuals using XP, including our University. So you are not only blocking out all of the OS X and Linux users, but a lot of the Windows users as well. This alone should be a reasonable argument to allow Qt development for Windows Phone.

(2) Support for existing Nokia developers. No need to explain.. This alone should be a reasonable argument to allow Qt development for Windows Phone.

(3) To future proof Nokia app-ecosystem. What ever the next distruption will be, and on what ever platform Nokia will build it, porting Qt to it should be easy. You’d have a reasonable amount of apps available rather fast as developers would only need to make minor adjustments and recompile. With the Microsoft’s history on these partnerships, this alone should be a reasonable argument to allow Qt development for Windows Phone.

(4) Qt and WP-development tools are simply very different and therefore speak to different kind of developers. There is no way you’d get all, or even most of the current Qt developers to pick up WP-development tools. Choise in development technologies/tools is not fragmentation, it’s versatility. When Nokia is not planning to ditch Qt anyway, this easily added developer value alone should be a reasonable argument to allow Qt development for Windows Phone.

Br. A student, a developer, a shareholder. Value of the future ecosystems, holder of blocked skills, owner of a plummeted portfolio. And I will publish my apps, for Nokia phones, or (actually) for A PLATFORM THAT I’M ALLOWED TO DEVELOPE FOR!

Tom says:

^^^^^^ Very good arguments in the post above me (“A student, a developer, a shareholder”) and that’s exactly why everybody is so angry with Nokia – although there are very good arguments for Qt Support on WP7 there won’t be upport. It’s obvious that it’s part of the deal (prerequisite from M$ for Nokia) that there won’t be Qt support.

Giorgio says:

I’m happy to have bought an android phone recently cause i was tired to wait for the long awaited Meego phone. Being a Qt developer (too) for many year I must admit I’m very disappointed with this Nokia decision and for sure I’ll give priority to development on Android from now on.

Yuriy says:

At first Qt has buried Jambi (MS and Java are incompatible)
Has then stopped operations over “Qt Eclipse Integration” – even help remained at level of version Qt-4.6.1 (MS and Linux are incompatible). QtCreator the release of the candidate hangs half-year in a state. And yes, precisely, now QtCreator to you it is not necessary. Saw qt-vs-addin-1.1.8.exe?
Sorry
msqt-msaddin-ms1.ms1.ms8.msexe – A code name “Qt everywhere”

cb says:

I have bought my new N8 because Nokia starts to be a verry
interesting, innovative company again. They had learned there leassons
and with QT, Ovi-Maps, Symbian/MeeGo and their commitment to OpenSource it was clear where Nokia will be in three years.
It was really an alternative to Apple/Android.

For people who defend Nokia again all bad forcats it ist pretty
hard to see how the board of directors is ruin this company and
all the hard work the people at nokia have made. Before the N8 was even out there was scandals about people leaving nokia and rumors about the future of symbian. ThE Management destroys the credibility of the speakers of the QT Developer Days. I believe in QT, but i don’t think that the Nokia Mamagement will give any attention to it now. With Elop, the board of directors has surrendered and give Nokia directly away to Microsoft. I can’t believe, that people can be that stupid, ignorant and coward.

Then, bad news adfter

Shmerl says:

@Steve: Some basic tools are free but are you saying that Visual Studio as a full blown IDE for .NET is free? I doubt that (though I never used it and don’t even plan to). But that’s not even the main point. The point is, that restricted toolset is used not to control quality – that’s just a lame excuse. It’s used to push off competing technologies. For example exactly for this reason Fennec (Mobile Firefox) couldn’t be ported to WP7 as well as to iOS. Normal systems don’t do this kind of junk, and provide normal full blown NDK.

Mwirigi says:

My perspective, from down here in Africa, where I imagine most of the “next billion” are supposed to disregard cheap Android phones and buy 150 million nokias, after what happened with Maemo, why should I have any confidence in Meego?

Lex Fridman says:

From the perspective of a Qt desktop developer, I am not at all worried about these news. Qt is quality, and quality products do not get abandoned. If Nokia abandons it, other companies will pick it up, and if not, I believe in the open source community’s ability to step up when needed. Trolls made Qt what it is, but that doesn’t mean without the core paid developers the project will not continue to grow.

Wojtek says:

What a disappointment – as a Qt developer for the past 6 years, I’ve rushed to buy N8 around Thanksgiving hoping to start new endeavor in the mobile space, just to learn a few days later that this “flagship” phone has OS that next gen phones won’t. Then, came a (sure) news about Symbian and (not so sure) about Qt. Now, I’m calling my N8 a “Titanic” – cool technology hit by an “iceberg”. Anyway, I guess we all are frustrated, but we will survive. I feel really sorry for Trolls though for a very well done Engineering (Qt) that doesn’t seem to be appreciated enough these days by whoever pays their salaries.
So, Trolls keep up your spirit and don’t give up, we need you guys.
-W.

thanyaluk says:

Qt is great with model/view programming and desktop app.

But it really lacks of Mobile UI which needs to be addressed.
– flickable class, should we need this? it should be built in with the SDK. any scrollable area should be able to do flick like other platform.
– message box, the symbian message box is rubbish for mobile app
– combo box, are you still stick with desktop style combo box?
– you can’t add button in the qlistview delegate which is a pain for me.

please rethink and redesign UI for Mobile. not just throw the desktop UI to the phone. thats not how it work these days

QML doesnt help if the standard UI sucks! i as on of the developers has to code everything by myself. there is no Good standard GUI that i want to use. please sort it out

regards,

Qt is dead says:

Translation: Qt is dead.
Switch to GTK+ 3.0, which is truly FREE and will not be in Microkia’s claws.

http://www.gtk.org/

Toledo says:

For another truly free GUI toolkit, but also truly native and truly C++ consider wxWidgets.

speak truth says:

GTK? wxWidgets?

Thanks, but no, thanks.

Qt will stay alive.
Folks, your really getting too pessimist!

Patrick says:

I just don’t get the point of time they took this step. I mean Meego was finally shaping up and QT was gaining quite some momentum. And how are they supposed to replace all their Symbian phones they sell in the world outside of the US with WP7? I mean they make most of their money outside of the US and still this seems to be a decision based on the US market. Plus how are you going to build an ecosystem around somebody elses ecosystem?…

For all the People that are concerned about QT being killed… this might help:

http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php

of cource… the open source community wouldnt be able to continue to evolve QT at the same pace, what is really a shame,… but QT is really a nice toolkit right now! =)

Brad says:

Maybe its the chance for gtk.

yang says:

after check
http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php.

I also want to know clearly, Will KDE-QT continue support windows if Nokia not release new QT version ?

I have been coded on QT since 2004. I doubted to focus on QT after NOKIA-MICROSOFT grouped.

Developer says:

If Qt was dieing with sybiam, Nokia will lose all the belief for both developer and consumer!!!

eagleye says:

What i dont understand why did meego take so much time to come up or will take so much time to come up..why cant nokia use up the great troll resources and bring up the platform which could be the android killer…now anyway nokia is a subsidary of m$

jm says:

Stop whining people !!!! Fight for Your ecosystem.

QT and Meego has a lot of potential and it WILL have a future, if _You_ do not let it fail. Do not lose Your hope. If You give up who is going to stand for this ecosystem.

It is our responsibility, as a QT- and Linux programmers, to give this ecosystem a future and show to Elop that he made a huge mistake.

I will say to all of You programmers, “Now its time to put all Your effort to make QT and Meego the platform of the future!!!”

Bedna says:

a failing nokia has found an equal partner

David says:

Does this means that Qt for Mac, Linux, Windows in danger ? And what about Qt 4.8 ?

Marcus says:

After leaving Motorolla, I decided to buy a Nokia E71, just because of the free sync software and the free map navigation. I enjoyed the experience so much that at home we had 2 more Nokia. Despite the GPS reception problem with my wife’s N97, I was expecting to change my “old” E71 for a N8. But this back stab from Nokia I’ll hold the money in the bank and see what the future holds.

I really don’t mind if Nokia reduces the pace of Qt developing, at least until they can feel how this deal goes. I just do not want it to be killed. After buying my first E71, just because of the free map and sync programs, I actually got into a deeper contact with Qt and started to adopt it in my small projects, also inducing students and co-workers to use QtCreator as the basic tool to develop small programs necessary to our day-to-day tasks, nothing professional. Most of them agreed mainly because it is multi platform, creates very pleasant look and had a big company supporting it, and was C++. Now…. what will I tell them! :o)

Bill Gates says:

It’s a good news for me and thousands of windows developers.

MS’s software and dev tools are always the best.

Go to hell you QT guys. The money is always ours.

Loaden says:

So Bad News!

maple says:

It is bad news to hear nokia cooperate with MS, I would rather it use Android.

Max says:

Fire Stephen Elop NOW!!!!!!!!! He is the spy from M$. His mission is making Nokia to be OEM company of M$.

David says:

come oon guys, stop bitching. WP7 is a great OS. the problem is not in microsoft, but is in nokia who refused to support Qt as they should. Qt should not be targeted for limited amount of platforms such as Symbian or MeeGo, it has much much more potential, including desktops. So the best thing that can happen now is nokia to sell qt to some big players and everyone will be happy. At least, did you see Nokia WP7 prototypes, they are very stylish. For sure, I’m going to buy at least one 🙂

Sumit says:

Qt is best ever framework. Nokia will regret its decision in future. using WP7 will kill innovation and creativity at Nokia. Moreover Nokia has lost developers trust in it. I hope Qt survives on its our, it has a huge potential.

Nokia Plan B FTW says:

Go Nokia Plan B.

Make the traitors pay. 🙂

Gnoop says:

Hey,

Nokia is in wrong direction. Probably they will sink in to the sea in one or two years.

So Please dont kill Qt(because its superior to any UI framework).
Either give it to free-software community or KDE or an opensource company.

Mark Vydra says:

What about this idea?
Microsoft wants the QT => wants opensource developers community which already exists around the QT. This is maybe the reason why MS cooperates with Nokia.

Qt Developer says:

I feel abandoned. Four years of my work went down the drain. I had always been a Nokia Fanboy and when Nokia bought Qt, I was happy. I dont have anything against MS or WP7, WP7 looks cool and all. Only if we could develop for WP7 using Qt 🙁

Foo Bar says:

I hate Microsoft and their war against Open Source. They are pathetic.

Developer says:

I will support Qt and Android in the future. Qt on the desktop and Android in the mobile. Qt is brilliant and will not die (Nokia will).

David says:

@Qt Developer
I’m not telling you to let go Qt, but did you give a try to Silverlight? If you are programming Qt for 4 years, you will get familliar with Silverlight in 1-2 days. Trust me, it a pleasure working with Silverlight just like working with Qt 🙂

@Foo Bar
What war? where’s the war? What does it mean war agains Open Source? Did M$ hire killers to kill linus? Am I missing something?

@Mark Vydra
Microsoft has already the largest dev community. Qt community is a drop in the ocean.

Tau says:

@David:

From Steve Ballmer himself : “Linux is a cancer”.

Good luck trying to convert the Qt community !

Also any platform that does not provide native development can only attract lame developers and applications.
The only way WP could compete is to provide a native SDK in C++ then it would have a better chance to attract serious developers.

Anyway, soon Intel chips will run Windows 8 on desktops, tablets and smartphones so the WP platform is already dead.
Stick to C++ and wait for Windows 8.
There are already smartphones running Windows XP and Windows 7.
Processing power is catching up very quickly and Windows 8 will be optimised to run on consumer devices including tablets and smartphones. Toy-ish platforms like WP have now a very short future (one year maximum).
Do not waste your time learning a new dev platform which won’t reach 5% of the market before disappearing.

Mk says:

Never liked M$ because it assimilates and monopolizes everything it touches. Felt so sorry for Nokia, it was a joke to hire Elop.

It really surprises me that Elop thinks Symbian cannot be revived, and than Win7 is the only cure to regaining market share. Just because your predecessor didn’t know how to develop the ecosystem doesn’t mean you can’t. Just an excuse to sabotage and assimilate Nokia from within.

Neglect FOSS and Symbian supporters, instead of taking advantage of the momentum, you’ll consumed by the wrath unleash upon you instead. The dip in stock price is just a starting point.

Loaden says:

Qt like OpenOffice.org, and now we have LibreOffice, but what is the LibreQt?
WoW, here is:http://www.libreqt.org/

Paul Smith says:

I have used Qt on and off both under FOSS licenses and commercial licenses for desktop applications starting with Qt 2 for many years now and have found Qt to be an absolute joy to work with. Kudo’s to the Qt developers for their hard work and vision.

I have also found the support from Trolltech (pre Nokia) to be superb and wish all the Qt developers and support personel the best luck in this time of insecurity.

While I feel strongly that Elop has just made a terrible mistake for Nokia, I am hopeful for Qt. Not because Nokia isn’t likely going to eventually marginalize Qt but because the LGPL allows Qt to be easily forked and independently maintained should Nokia abandon it or otherwise do things with it that are not in the community’s best interest.

Having several killer apps that only run on WP7 is a good selling point for both Microsoft and Nokia. It’s definitely in Microsoft’s best interest if Qt does not run on WP7 because it allows Microsoft to create a nice walled garden for WP7. I am sure that eventually Nokia will be forced to fall in line with Microsoft’s world view and will let Qt rot on the vine, even if Nokia’s management does not believe so now.

Should Nokia let Qt rot on the vine, I have confidence that the larger community will fork Qt and continue to support it under the LGPL (possibly adding support for WP7 in spite of Nokia).

While Nokia has likely marginalized themselves badly in hopes of some short term gain, the LGPL gives me hope that Nokia’s mistake will not also marginalize Qt.

nokiaa what are you doing? says:

once upon a timee , i was sayig “meego and qt and symbian qt super bla bla bla bla perfect for future bla bla bla…” and i was laughing to my android developer friends…….

BUT NOW…. anywayy…

Bones says:

I wonder what words of encouragement does Elop has for the thousands of Qt developers all around the word. All we hear is what Microsoft will pay Nokia for “killing” these large amount of it’s developers.
Why can’t Nokia continues it’s regular support for Symbian device using both WP7 and Symbian3 are it’s primary platforms? there should be a gradual introduction of Nokia’s support for WP7 and then they check the general customer’s attraction to Nokia’s WP7 phones and not what they are having now by having a gradual termination of the Symbian platform.
I was watching a Qt Apps demo at the Mobile world Congress in Barcelona and I was so so inspired by the Qt application displayed, people were talking about and so much interested in Nokia’s release of such device.
I am not against Nokia using the WP7 platform but using it as it’s only (!=primary) platform is a big insult to thousands of it’s skilled, trusted and loyal developers all because Elop is having an hidden Microsoft’s agenda.
I believe this Elop guy has no experience the the Mobile phone business or is he aware of Nokia’s dealings in the past couple of years trying to support it’s proprietary platform. Qt has come a long way and has become the phone’s market dream. The demand for Microsoft’s software developing tools was going down in favour of Qt’s easy to use tools, and all we hear is how much Microsoft is paying to kill these tools.
Qt’s (TrollTech) guys are recently supporting this Nokia-Microsoft’s deal because they have recently been told by their boss to shut-up and lie to us the developers.
Motorola recently released a beautiful cheap device powered by the WP7 and other phone producers are doing the same. theey are already building up a reputation for WP7 phones before Nokia comes to the market. I wonder what long term goal Elop plans to achieve. A regular customer will not buy a Nokia WP7 when he can get the same features in a similar and cheaper Motorola phone and have access to the same Microsoft’s “Ovi-store”.
When Nokia starts it full support for WP7 the market demand will go mainly to Motorola, Microsoft’s phones and other phone vendors. I see no future of Nokia in the next couple of years. the financial gains of WP7 devices will go primarily to Microsoft(for the OS) and Motorola cheap phones(because the hardware), Customers will see no uniqueness in Nokia phones both in hardware and OS.
Elop think twice!!!

You all need to chill a bit says:

This has to be the longest thread ever anywhere.

Still, wondering what is so disgusting in moving to .NET ?
I’ll bet the Visual Studio developing environment with .net is better than Qt.

Dinosaurs have to change, or deminish. You all Qute developers are in a good position to move into an easier development environment (ecosystem) than what was. Remember WP works on all platforms (mobiles, tabs, laptops, etc).

Basicos says:

You all need a Linus Torvalds who make the NUCLEUS of THE port of Qt INTO Android & IOS. It looks only translating into C.. so to go back into roots. Is not Qt made in C also, can you not reverse engineering Qt results?
Qt can become a new development language which rocks.

Basicos says:

It looks like TO fight for a finnland pride, to recover its honour, of Nokia´s “robbery”,
to develop a better shinning app than .Net, To make a libreqt or something alike to bring MS out of programming, and leave MS alone into WIN8 OS (enough work).

Josef says:

Bad news. I hope, there will be another mobile devices producer who’ll decide for qt.

Jano says:

And Nokia continue shooting to their feets… Qt for mobiles could be awersome but 1) Ovi Store is a crap and 2) Nokia is stopping Qt.

NuShrike says:

You know something is wrong with Qt’s development when Chrome, Firefox4, and IE9 have ALL beat Qt to an optimized, hardware-accelerated rendering backend.

It would be faster dev with better performance to write a UI in HTML5 in those browsers than Qt.

QClassified says:

I think qt is the best framework around and ive come from .net .

ive just discovered it and im lovin it, so simple but extremely powerful, beats the crap out of mfc and any other framework i tryed….the only problem with qt is the damn Q in front of every name 😀

Zlatan says:

Aron (Nokia) February 12, 2011 at 2:30 pm

Chris Browet: I hope I qualify as a “real Qt guy” (started in TT in July 2000). Qt does have a future at Nokia. That is why we continue to fund development and hire new people.

Mar 07, 2011:
http://www.gsmarena.com/nokia_is_selling_qt_commercial_licensing_and_services_to_digia-news-2396.php

IN. YOUR. FACE.

Hardeep Singh says:

“Nokia also announced it will ship its first MeeGo-related device in 2011, which will rely on the Qt ecosystem – and then will continue with MeeGo as an open source project for future disruption. Nokia can’t afford to be behind the next disruption again and Qt can play an important role in making sure it isn’t.”

I read this as “Meego isn’t ready yet, we’ll win the world with it and create the next disruption when its ready. Till that time we’re going to use Microsoft’s WP7 to ensure we don’t go bankrupt.”

Daniel Senior Developer says:

Just because some phones are selling super moderately Nokia gets scared and goes into a partnership. In many cases, nevertheless led to the ruin. I have seen this many times.
I once had a lot of sympathy with Symbian and other alternative OS’s. Therefore I had only bought Nokia phones. Emotionally i don’t like Microsoft and Apple. This is politics at all and not phun.
Establishing an open source mobile OS (embedded Linux with Qt) will be great! Im sure this can become even better, faster, smoother than all other commercial phones. My emotions are only correct if I have control over my own phone. We all know that Microsoft and Apple work together with the secret services and collects data from our desktop or mobile device.
No secure software shoould be written in IL (C #, VB.N). C # is not a new paradigm, but a programming language among many.
Let the developers decide what they like! Finally, we make the dirty work.

You really make it appear really easy along with your presentation however I to find this topic to be really one thing that I think I would never understand. It kind of feels too complex and extremely vast for me. I am looking forward in your subsequent put up, I will try to get the grasp of it!

Commenting closed.

Get started today with Qt Download now