Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nokia to developers: no Qt for Windows Phone development

engadget.com

Post reply on HN
Print view View original

11–20 of 69 posts

Re: Nokia to developers: no Qt for Windows Phone development

#11

Post by abdulla »

dawgr wrote: post #6
0x44 wrote: post #4

Earlier quoted context omitted.

C++ is one of the languages blessed by Apple in addition to C, Objective-C, and Javascript.

If they were going to switch to iOS, can't they just switch to Objective-C too even if they used to work with C++ before?

They have very different programming models, think Simula versus Smalltalk. You can use the two-headed beast that is Objective-C++, but there's varying levels of compatibility between the languages (in the 64 bit ABI, they share exceptions, in the 32 bit, they don't) and other various oddities they essentially mean they still remain two separate languages that have been kludged together.

Re: Nokia to developers: no Qt for Windows Phone development

#12

Post by JonoW »

tomh- wrote: post #5
JonoW wrote: post #3

Earlier quoted context omitted.

I thought neither iOS or Android use C++?

Android now offers the possibility to create entire apps in C++ using the NDK. On iOS you can also use C++.

I did not know that :) So if you can use C++ on iOS, why the hell are people using the horror that is Objective-C?

Re: Nokia to developers: no Qt for Windows Phone development

#13

Post by Tuna-Fish »

justincormack wrote: post #9
tomh- wrote: post #2

So, what will happen? 1) Qt c++ devs will invest in Visual Studio and learn silverlight/XNA or 2) Qt c++ devs simply switch to c++ development for iOS + Android

I cant imagine anyone switching to Silverlight now, its already dying, as MS have admitted, they only cant kill it before they release HTML5 for WP7 later this year.

Silverlight on the web is dead, but MS is pushing it hard as a local app platform, and for business applications. In those segments, it's far from dead.

Re: Nokia to developers: no Qt for Windows Phone development

#14

Post by oscardelben »

JonoW wrote: post #12
tomh- wrote: post #5

Earlier quoted context omitted.

Android now offers the possibility to create entire apps in C++ using the NDK. On iOS you can also use C++.

I did not know that :) So if you can use C++ on iOS, why the hell are people using the horror that is Objective-C?

Because Objective-C is far from being an horror language, but perhaps your impression (and so mine) is conditioned by your past experience with your languages of choice.

Re: Nokia to developers: no Qt for Windows Phone development

#15

Post by veeti »

tomh- wrote: post #5
JonoW wrote: post #3

Earlier quoted context omitted.

I thought neither iOS or Android use C++?

Android now offers the possibility to create entire apps in C++ using the NDK. On iOS you can also use C++.

Does the new NDK actually provide access to the UI API's?

Re: Nokia to developers: no Qt for Windows Phone development

#16

Post by mambodog »

JonoW wrote: post #12
tomh- wrote: post #5

Earlier quoted context omitted.

Android now offers the possibility to create entire apps in C++ using the NDK. On iOS you can also use C++.

I did not know that :) So if you can use C++ on iOS, why the hell are people using the horror that is Objective-C?

On iOS C++ is generally only used when you don't need to make much use of the Cocoa Touch APIs. If you do, you will be using the hybrid 'Objective-C++' language, and you will still need to use some Objective-C.

See this Stackoverflow answer: http://stackoverflow.com/questions/3804219/what-is-the-diffe...

Basically, it's probably easier and less messy to just learn Obj-C.

Re: Nokia to developers: no Qt for Windows Phone development

#19

Post by statictype »

JonoW wrote: post #12
tomh- wrote: post #5

Earlier quoted context omitted.

Android now offers the possibility to create entire apps in C++ using the NDK. On iOS you can also use C++.

I did not know that :) So if you can use C++ on iOS, why the hell are people using the horror that is Objective-C?

As ugly and annoying as Objective-C is, I find it's still an order of magnitude better than C++.
Post reply on HN