macOS Ever changing SDK issue

[nashyo]

I can accept that it is going to take me a long while to learn Objective C, and eventually writing apps for IOS. But how does experienced app developers deal with an ever changing SDK ?

There seems to be Beta updates all the time, and of course, a new iPhone every 1-3 years. Aren't the changes overwhelming?

 

[gnasher729]

i can accept that it is going to take me a long while to learn objective c, and eventually writing apps for ios. But how does experienced app developers deal with an ever changing sdk ?

There seems to be beta updates all the time, and of course, a new iphone every 1-3 years. Aren't the changes overwhelming?

No. You can ignore betas, and you can ignore new OS versions until the one you use doesn't work on the latest device anymore.

And if you have done any object oriented programming before, and if you can read a manual, then learning Objective C doesn't take long.

 

[Mac_Max]

Core APIs don't change very often in any good environment. For example, until 10.5 I could compile and run a lot of NeXTStep/OpenStep software from the GNUStep site on my Mac. Most developers won't ever use every facet of the SDK's class library, but if they do, they only use some parts once.

 

[mduser63]

New things tend to be added faster than old things are removed. So, while you lose out on using new features if you don't lose the new things, the knowledge you have tends to stay valid for quite a while. For example, I write and sell an app that I started writing around the time OS X 10.4 Tiger came out (2005). The latest version still runs on Tiger. Nothing it takes advantage of is unavailable in Lion, so it runs on Lion just fine too.

It's often fun to learn and use new APIs. Once you're comfortable with Objective-C and Cocoa, you'll find that it's not really that difficult to keep up.