logoalt Hacker News

ljmtoday at 11:44 AM1 replyview on HN

Kotlin is practically a no-brainer when you have JVM at your finger tips, versus something like Swift which is comparatively young.

I tried to use Vapor with Swift recently and struggled to get something working because the documentation looked comprehensive, but had a lot of gaps. I ended up throwing it out because I didn't have the time to dig through the source to understand how to do something, when I could use a mature framework in any other language instead.

The promise is there but I'm just not ready to invest. My youthful days of unbounded curiosity are coming to an end and these days I just want to get something done without much faff.


Replies

well_ackshuallytoday at 11:57 AM

Mind you, Kotlin/Native (which is what gets used when you're compiling for iOS) doesn't have access to the JVM.

However, the Kotlin community is fundamentally all about open source, whereas Apple & iOS Devs have an allergy to it. The quality and quantity is already miles above the vast majority of what's in the Swift ecosystem. https://klibs.io has all the native compatible libs. And if you're targeting a platform where the JVM is available then yeah, it's massive. Compose makes UI tolerable compared to JWT too. Even large projects like Spring are Kotlin first nowadays.

show 1 reply