Linked by Thom Holwerda on Wed 20th Jun 2012 18:38 UTC
Windows So, Windows Phone 7.5. I love it - warts and all. It has its issues, but it's so distinctive and fun it's pretty hard to not like it. So, for me, those three other people, and that cow, Microsoft today announced Windows Phone 8. It brings lots of cool new features, is built upon the Windows NT kernel and shares much of its lower levels with Windows 8, and oh, not a single current Windows Phone 7 device will be upgraded to it.
Thread beginning with comment 523142
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Mixed feelings
by moondevil on Thu 21st Jun 2012 09:35 UTC in reply to "RE[5]: Mixed feelings"
moondevil
Member since:
2005-07-08

The point being that Objective-C current success is due to iOS,

Developers that want to target native development in iOS and keep their costs low have to resort to one of the native supported languages, C, C++ and Objective-C.

With Objective-C being a requirement if the application needs to use the UI.

So like in JavaScript's case, Objective-C's adoption follows iOS adoption. This is not representative of the language quality as such.

Edited 2012-06-21 09:36 UTC

Reply Parent Score: 2

RE[7]: Mixed feelings
by tomcat on Sat 23rd Jun 2012 02:08 in reply to "RE[6]: Mixed feelings"
tomcat Member since:
2006-01-06

Objective-C is a horrible language, in my opinion. The only possible reason that Apple could have chosen it -- it couldn't be for productivity -- is to lock you into their platform. Nobody else on the freaking planet would be dumb enough to voluntarily use it.

Reply Parent Score: 2

RE[8]: Mixed feelings
by moondevil on Sat 23rd Jun 2012 07:31 in reply to "RE[7]: Mixed feelings"
moondevil Member since:
2005-07-08

My first contact with Objective-C was when I needed to port a graphics framework from NeXT to Windows/C++ back in 1999.

I kind of fell in love with the language in those days, specially due to the blend of C/Smalltalk features.

Even Apple was not so sure if developers would like to pick NeXT's system language, as in the beginning Java APIs were also made available.

As the developer community in Mac OS X decided to invest their time on Objective-C, the Java APIs were dropped.

Currently I see a few issues with Objective-C.

- Lack of modules or namespaces (C is to blame for this)
- Better ways to manage memory (GC never quite worked, ARC kind of works just with some Cocoa libraries)
- Even with GNUstep/clang, it remains a Mac OS X only language

Reply Parent Score: 2