1. Cross‑platform ambitions
- “Swift 6.3 includes the first official release of the Swift SDK for Android.” – ttflee
- “I don’t know. Could be nice for those developers that prioritize iOS and now they could keep writing Swift also for Android.” – victorbjorklund
- “The language doesn’t really matter. The underlying SDK/framework is where the action is at.” – ChrisMarshallNY
2. Growing language complexity
- “Swift is designed to be the language you reach for at every layer of the software stack… Such wasted opportunity by Apple.” – 0x3f
- “Why did this take so long to be added? Such strange priorities. Adding an entire C++ compiler for C++ interoperability before adding… C exports.” – sirwhinesalot
- “Swift has turned into a gigantic super complicated bag of special cases… We had a ton of users, it had a ton of internal technical debt… the whole team was behind.” – troupo
3. Ecosystem & adoption challenges
- “Kotlin has a pretty solid cross‑platform story… I’d pick it over Swift if targeting Android.” – iamcalledrob
- “A good source of available packages is the Swift Package Index… you can search here packages compatible with Linux.” – frizlab
- “Haven’t used it since v3 though… Swift could have easily dethroned Python… the letdown was on the Apple side – they didn’t bring in the community fast enough.” – dzonga
These three themes capture the main talking points: Swift’s cross‑platform push, concerns over its rapidly expanding complexity, and the practical hurdles facing broader adoption.