macOS Is it still worth it to learn Objective-C

[Partron22]

Swift will get at least the same level of support Applescript has over the years.
Maybe it'll get the same support ObjC has enjoyed.
It'll be a few years before we know, but ObjC will still be big among Apple developers after those years have passed.

 

[hiddenmarkov]

Swift will get at least the same level of support Applescript has over the years.
Maybe it'll get the same support ObjC has enjoyed.
It'll be a few years before we know, but ObjC will still be big among Apple developers after those years have passed.

I am thinking till apple programs have version x+1 swift coded apple will support obj-c, interally even. With version x+1 apple in swift they can then move older stuff to the security major bug patching phase, bug patching optional.

Since not prolific with final cut or aperture releases, and the office apps....I see obj-c even having a long life at even at apple.

Now apple could prove me wrong. And I dare them too....lol. If they gave us a new say aperture, now in swift, as a surprise in the fall I'd cowboy up and say I was wrong. I'd happily admit I was wrong in fact.


My working model for this is Microsoft. I'd be looking at .netframework. They put version X+1 on the wire, apps from Microsoft made for it hit the wire soon after. 3rd party gets the subtle hit that if the maker of the product is using it it be best to follow suit. If only because they know the now replaced framework is officially in the security only patch zone....there will be no further development for it. barring catastrophic bug, even bug patching is real iffy.

Apple is not not doing this. Or is not telling us which is usually apples way. In this case though it may backfire a little. Since the makers of the code, I have a slight interest to see in-house apps written by them. Even if beta. Apple made the language, well impress me with your skills applying it my reasoning.

This what I do with other langauges. I am learning R now. When I hit stack overflow for help and I see code snippets from people on core development team...I say to myself this is going to be good and look forward to seeing how good it gets.

 

[mrxak]

I could see Apple rewriting some of their more simplistic apps for Swift in Yosemite, and then over a period of years transition a lot of the rest pieces at a time. It'll just be like 64-bit, or Carbon to Cocoa.

 

[moonman239]

Swift can use Objective-C libraries, so there may or may not be much of a point in being able to code in Objective-C.

 

[JustinePaula]

Question: Where does an older person, almost 40 years old, with zero programming background start to learn how to make things for ipad/mac os x?

I have ideas about things I want to write, that is, apps I would like to see on the app store, as what I see on the app store does not do what I need it to do, I would like to make something unique for my needs and interests

Any ideas?

 

[ohbrilliance]

You'd first want to learn the fundamentals of programming. Ideally this would be using the Swift language, but it will take some time for material for beginners to come out. So for now you'd need to learn the basics in another language. That shouldn't be a problem, as the concepts can be applied between languages. (I studied C++ at uni and have only used other languages since).

The prerequisites for the excellent Stanford iOS course on iTunes U should be a good start. The first course is called Programming Methodology and the second Programming Abstractions. Both are available on iTunes U.
Otherwise, find some other sources for beginners's programming. I'm not sure whether the Objective C book by Big Nerd Ranch is for beginners, but it's worth a look.

 

[mrxak]

You'd first want to learn the fundamentals of programming. Ideally this would be using the Swift language, but it will take some time for material for beginners to come out. So for now you'd need to learn the basics in another language. That shouldn't be a problem, as the concepts can be applied between languages. (I studied C++ at uni and have only used other languages since).

The prerequisites for the excellent Stanford iOS course on iTunes U should be a good start. The first course is called Programming Methodology and the second Programming Abstractions. Both are available on iTunes U.
Otherwise, find some other sources for beginners's programming. I'm not sure whether the Objective C book by Big Nerd Ranch is for beginners, but it's worth a look.

I'll just add that you shouldn't worry too much about learning one language you're not intending to code with later. Some beginners worry about learning the "right" language, and avoiding the "wrong" language. In reality, learning more languages actually helps you, no matter what those languages are. Most of the logical concepts and data structures involved are identical across a wide variety of languages, they might just have different syntax and sometimes harder or softer rules governing their use. Learning the logical concepts and data structures in any language is essential to basically any other language you might learn later. So learn as many languages as you want/can, and it'll make it easier to learn Swift once there's some decent books out.

Also bear in mind, there's learning a language, and then there's learning the APIs (Application Programming Interface). For OS X and iOS, the APIs you'll need to learn are Cocoa and Cocoa Touch respectively (there's significant overlap). There's also other APIs that may be useful depending on what you're doing. Just learning a language like Swift will let you write great text-based terminal apps, but if you want to do GUI and stuff, you'll need to learn the APIs that let you do that. Hopefully once you get the basics of computer science down with whatever language you choose, there will be some good Cocoa books out there specifically designed around Swift code examples and so on.

 

[whooleytoo]

Swift can use Objective-C libraries, so there may or may not be much of a point in being able to code in Objective-C.

If you want to use C++ (lots of people have UI code in Obj-C with platform independent or performance-critical code in C++), you can't import C++ code into Swift, you need to use an Obj-C or C wrapper. That alone could mean lots of people will continue to use Obj-C.