Linked by Thom Holwerda on Fri 24th Sep 2010 23:20 UTC
Thread beginning with comment 442732
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-08
Regardless of the improvements Symbian has done in the last months to their operating system, if you want to directly target the platform, you still need to use the C++ dialect they have.
With all its quirks.
http://developer.symbian.org/wiki/index.php/Apps:Fundamentals_of_Sy...
Now compare this with the ease of the development of iOS, Linux or Bada. No wonder developers are leaving the platform.
Sure Open C/C++ and Qt do help minimize the pain, but you cannot target all handsets with them, and for some stuff you still need to go down to Symbian C++ anyway.
The funny thing is that the developer community was expecting that Symbiam would provide proper C++ support when the S60 3rd edition was introduced. The main reason being that they were breaking the operating system ABI, so the hope was there.
But no, the ABI was broken to introduce the DRM management features of having to sign API calls depending on the application capabilities in use.
Symbian^3 is going to be out real soon, and Symbian^5 is around the corner, and guess what Symbian C++ is still there.
So no wonder the companies move to operating systems that are more easy to develop for.