4 ms·
It's important to remember that Apple shipped both the Ruby and Python Objective-C bridges in ~10.5 era OS X. You can (and I have) written OS X native software
by jfb 13y ago
It's important to remember that Apple shipped both the Ruby and Python Objective-C bridges in ~10.5 era OS X. You can (and I have) written OS X native software in Python; it wasn't super pretty, but the concepts mapped across reasonably well.
So I wouldn't take this as necessarily the sign of a shift in anything.
- dottrap 13y agoAlso, people at Apple like Objective-C and its Smalltalk influences. For those of us who've been in the NeXT/Apple ecosystem a long time, it's clear that employees at Apple see Ruby as more interesting than say Javascript because of the Smalltalk influences. If any shift were to occur, money is on Ruby. But Apple likes Objective-C and no shift seems likely and we also saw what happened with MacRuby and the author leaving to do RubyMotion.
- jfb 13y agoAnd they've invested a lot in the tooling and environment. It's not like they're just running a stock gcc toolchain; they've put a lot of very smart people on very hard problems in the language space.
- dottrap 13y agoAgreed. And another problem is that all these interpreted languages are terrible at exploiting parallelism which is a problem as we get more processor cores. They were able to solve this in C by inventing Blocks and GCD.
- Moto7451 13y agoThey used to have a Java bridge as well[1]. WebObjects moved from Objective C to Java at some point in the early '00s. [1]http://cocoadevcentral.com/articles/000024.php http://cocoadevcentral.com/articles/000024.php