Kotlin Native for CLIs by Ryan Harter

[@StEvUgnIn]

The authors of GCJ already identified that compiling java natively was slower than JIT compilation on the JVM. Thanks Ryan for pointing out the truth again. The only way to improve Kotlin Native would be a redesign similar to Go.

[@StEvUgnIn]

I am pretty sure there is an option on gradle to rename the CLI, Ryan.

[@drizer4real]

seems to me that the static option was the least hassel

[@georgeshalvashvili6270]

why not use memScoped { } ?

[@georgeshalvashvili6270]

at 34:11 It's strange why JVM is so fast. An explanation would be great. maybe it is because of the library? The last time I tried to print Hello World with a JVM it took like 3 seconds because it had to start the JVM and then print the text.

[@shahriarzaman4715]

I thought it was K/N stuff. But it turned out JVM stuff. :(

[@Bozacar]

You could have used Graal native image to compile to native executable. One binary and also fast

[@gregandark8571]

Why using GRaal if Kotlin is already capable at native???

[@Bozacar]

@@gregandark8571 Because KN is much more limited in terms of libraries. And is less mature

[@gregandark8571]

@@Bozacar I guess that you're right,because i'm actually struggling to understand Kotlin NATIVE.

[@AngelDMunoz]

Nitpick: The talk us going great so far but what's with the windows diss though? It sounds just like the "jvm is so slow" stuff, both ideas are pre-conceptions of old which aren't really true these days and both the jvm and windows are great IMO Other than that this talk is very very cool, I feel like trying the kotlin native side of things but also happy to stay in the jvm side unless I really need to, it shows that if you need native you really have to put in a little bit more the effort to be sure you have actual performance gains Kudos for the talk really well put!

[@mondoshigua]

👋🏻🇨🇴🧔🏻👍🏻🤝🏻