3 ms·
Same. Also at least based on what I’ve seen on Android there’s a decent chance you’ll be stuck using some Java libs due to lack of native Kotlin counterparts, w
by jwells89 3y ago
Same. Also at least based on what I’ve seen on Android there’s a decent chance you’ll be stuck using some Java libs due to lack of native Kotlin counterparts, which makes it harder to fully leverage Kotlin’s features wherever you need to work with those libraries.
The syntactically similar language I’d rather have run everywhere is Swift. Swift Package Manager has problems too of course but in my experience has been less maddening, and the community has been more aggressive about writing native Swift replacements for Obj-C libraries.
- wiseowise 3y ago> which makes it harder to fully leverage Kotlin’s features wherever you need to work with those libraries. What does this even mean?
- jwells89 3y agoJust that Java libraries aren’t going to be taking advantage of Kotlin-specific language features, which in turn makes it harder to use those features in the parts of your application code that interact with those libraries unless you write wrappers that make these libraries fit in better with your Kotlin codebase. There’s a similar issues with using Objective-C and C libraries in Swift, which makes Swift libraries more appealing where available despite Obj-C/C interop being good.
- wiseowise 3y agoYou didn’t answer my question, just rephrased your original message. The only case I can think of is wrapping callbacks with coroutines, everything else will work in Kotlin out of the box.