4 ms·
I'm not that concerned with Apple's purposes. You could pick a third of the languages on this list and improve on Obj-C: http://www.tiobe.com/index.php/content
by SideburnsOfDoom 12y ago
I'm not that concerned with Apple's purposes.
You could pick a third of the languages on this list and improve on Obj-C: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
Or rust, D or go which you mentioned elsewhere. None of therm are ideal, all of them are > ObjC
You could have an open ecosystem where all of them exist. That you don't is an indication of how "Apple's purposes" diverge from programmers' purposes.
- rsynnott 12y ago> You could have an open ecosystem where all of them exist. That you don't... But you do, at least for two of them (D doesn't seem to support ARM yet). Here's Rust: https://github.com/rust-lang/rust/wiki/Doc-building-for-ios https://github.com/rust-lang/rust/wiki/Doc-building-for-ios And here's Go: https://bitbucket.org/minux/goios/wiki/Home https://bitbucket.org/minux/goios/wiki/Home Or you could write your iOS app in C, or C++, or Python, or... In all cases, you'll be calling objc_send a lot, and that's the problem. A Swift class can subclass an Objective C class, and implement Objective C protocols; good luck with that in a language with an incompatible object system. Apple isn't stopping anyone from using those languages; it's just that adopting them would make very little sense; using existing APIs and third party libraries would be horrendous.
- SideburnsOfDoom 12y ago> Apple isn't stopping anyone from using those languages; it's just that adopting them would make very little sense Apple isn't stopping anyone, and Apple certainly isn't encouraging anyone from using any language that doesn't issue forth from Apple.