|
|
|
|
|
by wruza
855 days ago
|
|
I don't develop for Apple anymore, but tried swift ecosystem once, wasn't impressed. ObjC does its job, and I'm from the camp named "if it does the job and has no obvious limitations, there's no reason to switch". It's a mature language that works, and I know both C and ObjC, and the whole system is native to these two. What else would I need? I think I could answer this question, but the answer isn't Swift. If I'll have to do Apple again, I'll start with ObjC, unless it becomes completely abandoned at the time. |
|