why everybody’s trying native with obj-c instead o...
# kotlin-native
c
why everybody’s trying native with obj-c instead of swift? With swift the only problem I faced was incompatibility with khttp (so I couldn’t work with REST), but everything else was fine
l
Swift runtime makes the apps bigger
Download size is under 10m, which is pretty good for iOS. Swift doesn’t add as much size as it used to. The releases are less frequent so you don’t really have to include runtime with you app. They’re on the phone already
👍 1
l
If they can include Swift runtime into iOS for apps to use, they may do it for Kotlin/Native too one day (if the releases get less frequent, though I doubt they would ever consider it under Tim Cook)
k
No way that’s ever happening
c
@kpgalligan cheers for share, what library you use for http requests? I’m willing to start my own path with native soon, but unfortunately not many information can be found on the internet 😞
k
Just a simple get expect/actual for now. Ran into gradle issues with ktor, but now that conference is over ( 😞 ), going to update with latest libs and (hopefully soon) multithreaded coroutines.
c
how do you face gradle problems? I’m still having some, changing versions didn’t work and I’ve came to conclusion that some libraries are simply incompatible with native
Multithreaded on mobile? Sounds impressive tho
k
Didn't fix gradle issues with ktor, which is why I wasn't using it. Going to look at that soon (conference ended today, so going to sleep first)
c
ah ok, hope one day kotlin native would become greater or at least stand on a same stage with android’s brother 🙂