>Out of all the binaries in iOS 15:

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.

Wouldn't most binaries not have UI anyways? Probably better to compare Swift UI to previous UI frameworks.

Swift was conceived and sold as an all purpose language. To an extreme degree, in fact. Lattner has said many times that it's intended from scripting to system programing[1]. Currently it's good at neither.

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’ve had very few complaints with Swift as a backend language in all honesty.

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.