Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I get this argument for any other company.

But at this point Apple has gone to great lengths to control the entire toolchain from the OS to the compiler to the chips that run the instructions the compiler produces.

It’d seem odd if they didn’t go with something home-grown as their language of choice.



But it would be better for a lot of developers who don't want to spend a lot of time learning ObjC just for iPhones. It might also have been a safer choice for Apple since they now are in a bit of a danger if iPhone and iPad sales goes down. Then the number of developer learning their languages might fall fast and then the app ecosystem might start to fall too.


ObjC is about as homegrown as it gets. There are few major uses of ObjC outside of Apple/NextSteps's ecosystem.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: