Would I honestly post all that if I knew it wasn't true? Of course I wouldn't!
So let me put it in others words: please enlighten me as to my errors.
Here we go again...
- C++ is severely limited in iOS and Android for anything that touches the platform SDK. This mean, among others things, that any interaction with the UI cannot be done in straight C++ and needs to hook to Java or Objective-C. Also none of these platforms recommend the use of C++. On the contrary. Prove us they are.
- What smartphones are these in which C++ is the recommended language? Symbian. What else? You used the plural. What other platforms are these? Prove us.
- You obviously don't know what Nokia's CEO Stephen Elop has said about it's own Symbian platform just before signing with Microsoft for the adoption of Windows Phone 7 and eventual removal of Symbian from Nokia's product line.
- There's no plans to bring Qt into Android. Where did you get that idea? Show it to us. What there are is two community-made ports that sort of work when its not raining. Neither it is clear what use can be made of Qt in Android since the NDK is still only a subset of the SDK; a companion tool, not a replacement. Also, C/C++ application on the Android still run inside a VM. There's no native code running inside Android. All this means the use of C or C++ on the Android platform is limited to specific cases and not recommended for all other cases. Qt is a rather useless addition that brings nothing to new to the already existing Android's UI framework.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I put in "not verified" because I wasn't totally sure. But I have heard that C/C++ are among the recommended languages for the platform in the sense that it is some of the languages that can be used to develop for the platform (as opposed to things such as Flash, which adobe tried to make a converter for that was shut down by Apple some time ago; don't know what became of it after).
Yes, I do know of it. But that's several years down the line. At least 4 years before Symbian is not supported any longer. And Symbian is growing at a terrific pace at the moment which isn't slowing down.- You obviously don't know what Nokia's CEO Stephen Elop has said about it's own Symbian platform just before signing with Microsoft for the adoption of Windows Phone 7 and eventual removal of Symbian from Nokia's product line.
I did not say official. Likely there will be a community effort, however.- There's no plans to bring Qt into Android. Where did you get that idea? Show it to us. What there are is two community-made ports that sort of work when its not raining. Neither it is clear what use can be made of Qt in Android since the NDK is still only a subset of the SDK; a companion tool, not a replacement. Also, C/C++ application on the Android still run inside a VM. There's no native code running inside Android. All this means the use of C or C++ on the Android platform is limited to specific cases and not recommended for all other cases. Qt is a rather useless addition that brings nothing to new to the already existing Android's UI framework.
I do know that Java is generally frowned upon on Symbian.
Are we all straightened out then? Right or wrong, discussion or not, the point is to bring out points to the OP, and not be some encyclopedia.
Continued support for the Symbian platform is completely irrelevant, as Nokia already announced 2011 and 2012 to be the years of transition. Ideally, by the end of 2012 only those markets where Windows Phone 7 is not localized yet will have Symbian phones. Symbian can be supported until 2100 for all we care, it just won't be sold inside a smartphone in 2 years. Or so is the plan. An update to Symbian is expected this Summer, and that may be the last major update to the platform. On the other hand, the announced death of this platform is reason enough to stop developing for it, so while Nokia may still be committed to support it, app developers will (should, and some are already) migrating. Meanwhile, a couple of weeks ago Nokia closed the source for Symbian, thus putting another nail in the coffin of this platform.
So what? Symbian is not the only smartphone platform. It's not even one that matters. It's dead.I do know that Java is generally frowned upon on Symbian.
Really? You start you post accusing others in here of "lots of misconceptions" and go on about to produce clearly wrong points on what became the worst contribution on this thread. You don't need to be an encyclopedia, we just ask you to know what you are talking about if you accuse others of misconceptions.Are we all straightened out then? Right or wrong, discussion or not, the point is to bring out points to the OP, and not be some encyclopedia.
Meanwhile you edit your initial post on grounds of "negative feedback" as you put it, removing all the rubbish you wrote and any sense to this discussion. That's below the belt, but something that I came to know about you. Just don't think it goes unnoticed the fact you deliberately remove context by editi8ng your previous posts, every time the discussion doesn't go the way you planned. A simple retraction would have put on on a much higher light.
Last edited by Mario F.; 04-23-2011 at 05:42 PM.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I'm sorry, no, that's just wrong.
The Symbian base will grow and grow even more in the coming years. You must have heard how many more Symbian phones are going to be sold. That's reason enough to develop for it, now more than ever.
And Symbian won't die that easily. It will likely be pushed down to non-smartphones in the coming future, making it still important.