4 ms·
Android will eventually adopt Swift. It is not a matter of "if" but "when". Who knows 5 year from now, you all will be coding in Swift (for servers, iOS and And
by awaisraad 9y ago
Android will eventually adopt Swift. It is not a matter of "if" but "when". Who knows 5 year from now, you all will be coding in Swift (for servers, iOS and Android).
- PeterisP 9y agoCan you list arguments why do you believe this to be likely? Interoperability of Swift with the existing APIs and JVM is not impossible, but it is a significant barrier that needs to be overcome and needs very, very significant advantages to justify that.
- awaisraad 9y agoWatch: https://news.realm.io/news/tryswift-chris-robert-end-to-end-application-development-swift-backend/ https://news.realm.io/news/tryswift-chris-robert-end-to-end-...
- PeterisP 9y agoIt doesn't seem to be particularly relevant; potential for server-side usage of Swift is one thing, but Swift apps for Android devices have quite different challenges and reasons for (non)adoption.
- swsieber 9y agoIMO, kotlin makes a much better candidate to be "the" cross platform language for server / client since it supports typescript as a first class citizen, and a native target is coming. You could use the same arguments in the article you posted to posit that everyone will be developing on a Mac. It's not very convincing to me.
- y_u_no_rust 9y agoSwift isn't even a stable language I can't even build projects from github that are only a few months old without doing some wank-tastic manual syntax conversion or using an old version of xcode no one wants to be held hostage to apples nuttery if it's avoidable even .net core and it's associated languages and frameworks are in much better positions
- deleted 9y ago[deleted]
- bitmapbrother 9y agoWith Kotlin on the JVM and Kotlin Native on Windows, Mac, Linux and iOS I really don't see much of a future for Swift outside of iOS. Kotlin, though, will be everywhere.
- yoz-y 9y agoI think both will find their place. Currently there are many languages that are interchangeable in many cases and yet they find their users. I suppose that Kotlin outside of JVM has a similar problem to Swift outside an Apple platform. You lose a support for quite a lot of already existing libraries. Rewriting everything in Kotlin and Swift will take effort and by the time we'll get there not many will want to abandon their preferred ecosystem.
- mikespikey 9y agoYour downvotes are due to the Jetbrains vote brigades here and on Reddit.