6 ms·
>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 Obje
by ksec 5y ago
>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.
- kgc 5y agoWouldn't most binaries not have UI anyways? Probably better to compare Swift UI to previous UI frameworks.
- tambourine_man 5y agoSwift 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/slashdots-interview-with-swift-creator-chris-lattner 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
- urthor 5y agoI’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.
- adamnemecek 5y ago> The fact the Foundation library is closed source is a complete joke in this day and age. Foundation is open source https://github.com/apple/swift-corelibs-foundation https://github.com/apple/swift-corelibs-foundation
- andrewjl 5y agoThe Foundation library on non-Apple platforms is open source: https://github.com/apple/swift-corelibs-foundation https://github.com/apple/swift-corelibs-foundation and intended to reach parity with the Apple version. > Our primary goal is to achieve implementation parity with Foundation on Apple platforms. This will help to enable the overall Swift goal of portability.
- lolinder 5y agoBut why are these even two separate libraries? Is it normal for different platforms to have different implementations of the standard library? I'd assumed that most of the library would have been written in Swift itself, which should theoretically make it be as platform-independent as Swift is.
- olliej 5y agoThis is assumption from first principles 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
- andrewjl 5y agoFoundation is not the standard library of Swift. Swift has its own standard library that is bundled with the language on all platforms that are supported. 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/Docs/Design.md#portability https://github.com/apple/swift-corelibs-foundation/blob/main...
- jollybean 5y agoIf it were extremely well documented with a lot of nice examples the open/closed nature of the libs would be a secondary question.
- KerrAvon 5y agoIt’s not impossible — Lisp exists and has been used in both contexts for decades. 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
- tambourine_man 5y agoHow successful are Lisp OSs?
- pjmlp 5y agoSometimes I think an Objective-C 3.0, that would break with some of more problematic C flaws would have been better, even though I dislike @ and [] everywhere.
- gurkendoktor 5y agoThe question is, where does ObjC end and where does Swift start? When Apple announced an Objective-C without the C, I assumed they'd keep the Smalltalk object system and message passing. It still boggles my mind that they took a hard turn into the world of value semantics and extremely static types, with all the ABI problems that we know from C++, plus all the interop hacks to bridge both worlds. The syntax almost seems like a superficial detail compared to the new object model. 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.
- pjmlp 5y agoNot sure if they bet the farm as such, there are plenty of rants regarding how unsuitable SwiftUI is outside iOS for macOS workflows.
- tambourine_man 5y agoCame here to post the same. We tend to spin around the shinny and new. These numbers, even if a but inaccurate, are sobering and show who's really running the show.
- deleted 5y ago[deleted]
- josephg 5y agoIf even Apple is writing more new software in Obj-C than they are in swift, its probably still a fantastic time to learn obj-c and use it to develop applications. Or at the very least, use Swift + UIKit rather than SwiftUI.
- jollybean 5y agoI think this the wrong take from the data. 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.
- gurkendoktor 5y ago> But for outside devs, Apple has almost frozen ObjC in favour of Swift 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.
- deleted 5y ago[deleted]
- madeofpalk 5y agoThey have like, at a minimum, 10+ years of a whole OS built on objc. Of course it's going to be a high percentage. I would be weary of any team who decided to rewrite an OS in an emerging language.
- deleted 5y ago[deleted]
- pjmlp 5y agoMore like 20+ given the NeXT heritage.