Live data from Hacker News

Nokia to developers: no Qt for Windows Phone development

engadget.com

31–40 of 69 posts

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

#34
post #12
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 ... well ... you're uninformed and obj-c is not a horror?

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

#35

Earlier quoted context omitted.

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.

I can see Silverlight perhaps finding a niche in internal application development - but that's a pretty big come down from the original goals of the technology (i.e. a Flash killer). So wouldn't that make Silverlight, if not dead, severely wounded?

It would mean Microsoft has realized that competing for Flash's position is not worth the fight, effort or money as Flash and its position in general (plugin-based web-solutions) is losing grounds every single day. They are not willing to fight a battle which will eventually be lost anyway.

They are simply refocusing their efforts to get Silverlight (which is a pretty good piece of engineering IMO) put to use elsewhere.

As far as I can see, that is a pretty good strategic decision.

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

#36
post #22

Earlier quoted context omitted.

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.

I'm probably being unfair, I've never actually done any development in Objective-C (I have in C++), so I'm going on how it "looks" from the code I've seen, I just find it very unreadable. But in fairness I haven't tried to get into it, and I'm probably biased toward the C#/Java style syntax...

I neglected to give more than a cursory glance at Obj-C back when the iPhone 3G and app store first came out. I hugely regret it now, but I was doing C++ at the time and thought it was the cat's pajamas.

If you can think abstractly and use/like languages like Ruby and Lisp (and their reflection/metaprogramming features), I think you'll be surprised by the amount of stuff you can do at runtime in native code. I started doing Obj-C a week ago and am about to submit my first free, 90% custom-drawn control app to Apple for approval.

Yes, the syntax is initially unappealing, but you get over it after about a day. On top of that, Xcode + Interface Builder is the best GUI dev environment I've used yet.

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

#37
Learning moment: developers can't be wedded to a particular technology. Qt is fantastic but it's not the business. We can't invest ourselves in companies that are floundering and Nokia has been floundering for a number of years.

If you find yourself investing your talents in a company that has multiple directional changes you need to consider the likelihood that the company will ever return to good times.

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

#39
post #17

I just hope Qt doesn't die.

I don't hope so either. Although GTK is starting to look pretty nice with version 3, I've always preferred QT from both a a programming and UI perspective. Nokia seems truely cluesless.. every day, another strategy - Maemo was GTK based - Nokia bought TrollTech - Maemo was said to be ported to QT - Maemo was abandoned for Meego - Now they're giving up Meego, and going to MS... sigh

Word to the wise: When you're flailing, that's when self awareness is the hardest. It's also when it's most valuable.

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

#40

Earlier quoted context omitted.

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.

I can see Silverlight perhaps finding a niche in internal application development - but that's a pretty big come down from the original goals of the technology (i.e. a Flash killer). So wouldn't that make Silverlight, if not dead, severely wounded?

Silverlight is competing internally with Windows Azure. (Some potential synergy there as well.)
Post reply on HN