89% are using Objective-C
17% are using C++
13% are using Swift
8% are entirely written in C
2% are using SwiftUI
Objective C looks healthy.
89% are using Objective-C
17% are using C++
13% are using Swift
8% are entirely written in C
2% are using SwiftUI
Objective C looks healthy.
I would be weary of any team who decided to rewrite an OS in an emerging language.
I think a language that's simultaneously productive at this two extremes is impossible, but it was their goal.
[1] https://developers.slashdot.org/story/17/01/23/085232/slashd...
“In short, I would NOT say that Swift is an extremely compelling systems programming or scripting language today, but it does aspire to be great for this in the years ahead.”
Jan 2017
I can see it as a backend/systems language. It is not a scripting language.
The issue is the stewardship of the ecosystem.
The fact the Foundation library is closed source is a complete joke in this day and age.
Apple’s lack of effort towards fostering a broader community for its language is a comedy of errors.
A Swift developer will spend much time dealing with undocumented closed source packages.
It’s almost comedic how retro it is. It’s like coding in the 1980s.
> Our primary goal is to achieve implementation parity with Foundation on Apple platforms. This will help to enable the overall Swift goal of portability.
And Foundation itself isn't written in Swift, a good portion is written in C.
> A significant portion of the implementation of Foundation on Apple platforms is provided by another framework called CoreFoundation (a.k.a. CF). CF is written primarily in C and is very portable. Therefore we have chosen to use it for the internal implementation of Swift Foundation where possible. As CF is present on all platforms, we can use it to provide a common implementation everywhere.
https://github.com/apple/swift-corelibs-foundation/blob/main...
The Apple versions of foundation have to be compatible with the Foundation/CoreFoundation equivalents. They also have more than a decade of binary compat to maintain
Foundation is open source https://github.com/apple/swift-corelibs-foundation
On the other hand, the Smalltalk model would not have worked for SwiftUI. It really feels like Apple has bet the farm on the next generation of libraries/frameworks.
Swift needs some work to get there. There are a huge number of gaping holes, but these would be a start:
- scripting: a native RegEx literal type
- systems: replace Codable with something easier to use/more performant
- systems: better logging interface
Edit: formatting
It will be worth looking at the stats again in 2024, 10 years after Swift was introduced.
Or at the very least, use Swift + UIKit rather than SwiftUI.
Apple is writing 'more Obj-C' because it's their incumbent language, and they are 'writing a lot more software'. As the basis expands, it's going to expand along the normative vector, which is ObjC.
But for outside devs, Apple has almost frozen ObjC in favour of Swift, and Swift is 100% the future for apps built for iOS/MacOS.
Even externally, ObjC will probably be supported for a 'very long time' and maybe even perpetually at this point, it's really not the future.
Internally, the sands have not shifted, but I suggest that within about 5-7 years Swift will be on even footing with ObjC even within Apple.
So if you're an Apple focused Dev. not working for Apple ... then Swift is probably your #1 focus with a 'Healthy Knowledge' of ObjC - at least enough to access arcane and un-ported APIs as a nice thing to round out your skills.
ObjC is losing popularity, it will be a 'well supported' niche language going forward. You can probably bank on your ObjC skills for a long time to come, but in a more narrow range of opportunities.
In my experience, Apple doesn't even have to freeze anything because the iOS developer community (outside of Apple) is full of proud Early Adopters. Sometimes it feels like a race to use the latest tools on day one. I haven't seen anyone looking for ObjC developers from the day Swift was announced.
Modules that are complicated and not broken, are extremely expensive to fix esp. when they need to develop new stuff.
Legacy and backwards compatibility have a way of keeping things around.
It’s not in maintenance legacy mode. It’s thriving.
My bet is that even then, most ObjC use is due to legacy - most of those binaries are probably related to apps that are already in ObjC.
I looks like they plan to keep it around for the foreseeable future, but I wonder if it will mostly be eventually replaced by Swift for new starts.
Within 5-7 years Swift will rival ObjC within Apple, and from then on it's hard to tell.
There are no foreseeable plans to rewrite the OS, and so ObjC has to stay around, but that's in a clearly limited capacity.
[1] https://www.benfrederickson.com/ranking-programming-language...
But Metal will eventually be re-written. Not for a while, but eventually.
Objective-C will be just the same at Apple, specially since their creators decided to go search for other adventures outside Apple.
Very few companies can.