4 ms·
I learned Obj-C during the early days of the app store, probably 2009-2010. This was before the iPad came out, so I remember ARC being introduced. I really like
by Clubber 2y ago
I learned Obj-C during the early days of the app store, probably 2009-2010. This was before the iPad came out, so I remember ARC being introduced. I really liked it back then because code had to be so lean memory wise (compared to say Java or C#) and I had to deal with memory allocation and deallocation in the Delphi days, so I was comfortable with it. I published a few apps that were moderately successful (not FU money) then kinda got bored during the long tail of the cycle and didn't feel like upgrading the icons and images over and over again.
I never got onto the Swift train, it was too new when I stopped. I think I know the answer, but would you recommend Swift over Obj-C, for someone failingly familiar with Obj-C if I were to get back into the game? If so why or why not? Is it just as fast as Obj-C and is there anything I can't do with Swift that I could do with Obj-C?
- busymom0 2y agoI stuck around with objective C for a long time. Till around 2018/2019 when I finally built my first fully swift app. It was actually my hacker news app called HACK: https://apps.apple.com/ca/app/hack-for-yc-hacker-news-reader/id1464477788 https://apps.apple.com/ca/app/hack-for-yc-hacker-news-reader... I would highly recommend Swift over Objective C. It's a lot cleaner and therefore also fun. I still use objective c if I am using some old codebase but other than that, nowadays, I don't see any reason to start a new project I in objective c. You should really give Swift a try. Also, Android's Kotlin is also kinda fun similar to Swift.