I wish Kotlin would add support for dataarg (similar to vararg). It would make data classes more composable -- e.g. clone a data class with a few more fields without copying the full list of fields.
Yeah, haven't heard tooooo much about that yet! Maybe upvote and/or comment on the issue here: youtrack.jetbrains.com/issue/KT-8214/Allow-kind-of-vararg-but-for-data-class-parameter
Maybe check out skip.tools/ ... I haven't used it myself, but it does Swift -> Kotlin, including the UI layer. A few guys from Skip were on the Kotlin podcast recently talking about it: th-cam.com/video/mig81rSWVqM/w-d-xo.html
@@MonichGPT I remember someone at JetBrains saying that the goal is two-way export between Swift and Kotlin. Now they're working on Kotlin to Swift export, then they'll hopefully tackle the other way around. And the delay to this is perfectly understandable; they're trying to make two fundamentally different languages interop with each other. As much as Swift and Koltin look familiar, Swift is quite a beast compared to Kotlin, and functions a bit differently to Kotlin in the lower levels as well (e.g. GC vs. RC). So while Kotlin/Native runs basically at the same level as Swift code (and they both compile down to LLVM IR, and from there they look basically the same to LLVM), it's still quite the challenge to get these languages to "seamlessly" interop without much friction at the higher levels (APIs etc.).
I wish Kotlin would add support for dataarg (similar to vararg). It would make data classes more composable -- e.g. clone a data class with a few more fields without copying the full list of fields.
Why is it not here yet 😭
Yeah, haven't heard tooooo much about that yet! Maybe upvote and/or comment on the issue here: youtrack.jetbrains.com/issue/KT-8214/Allow-kind-of-vararg-but-for-data-class-parameter
It was mentioned in this talk (24 minute mark) that it will start in version 2.2: th-cam.com/video/tAGJ5zJXJ7w/w-d-xo.html
Community comments are great!
Thanks, Radek. Glad to know you liked that part - we'll plan to keep it as a regular segment! 👍
Swift export looks promising
As an experienced Android engineer. Should I learn multiplatform technical skills such as KMP, flutter, React Native. Which would be the best one.
I would go with KMP, you already know Android and Kotlin and the KMP stack seems to be growing fast.
@@delespai5592 Thank you bro, that makes sense.
Need swift to kotlin
Maybe check out skip.tools/ ... I haven't used it myself, but it does Swift -> Kotlin, including the UI layer. A few guys from Skip were on the Kotlin podcast recently talking about it: th-cam.com/video/mig81rSWVqM/w-d-xo.html
@@typealias This is "Swift Multiplatform" but I need to use swift code in shared Kotlin module.
@@MonichGPT I remember someone at JetBrains saying that the goal is two-way export between Swift and Kotlin. Now they're working on Kotlin to Swift export, then they'll hopefully tackle the other way around.
And the delay to this is perfectly understandable; they're trying to make two fundamentally different languages interop with each other. As much as Swift and Koltin look familiar, Swift is quite a beast compared to Kotlin, and functions a bit differently to Kotlin in the lower levels as well (e.g. GC vs. RC). So while Kotlin/Native runs basically at the same level as Swift code (and they both compile down to LLVM IR, and from there they look basically the same to LLVM), it's still quite the challenge to get these languages to "seamlessly" interop without much friction at the higher levels (APIs etc.).
just tell me how you are doing kotlin better than kotlin ?