Having a 150mb+ JAR full of weird compiler stuff (from jrtfs to Swing!) in kotlinc quite easily built with Native Image, and immediately yielding this kind of improvement is outstanding.
Looking forward to what's next 👀
> So far, a native image with PGO offers a properly "warmed-up" kotlinc and with up to 20% more peak throughput.
Ticket: youtrack.jetbrains.com/issue/KT-823...
Having a 150mb+ JAR full of weird compiler stuff (from jrtfs to Swing!) in kotlinc quite easily built with Native Image, and immediately yielding this kind of improvement is outstanding.
Looking forward to what's next 👀
A lot of work ahead, but it starts getting its shape 👀
A lot of work ahead, but it starts getting its shape 👀
@Sellmair did an amazing job -- explaining dynamic classloading, DCEVM, continuous builds, Compose internals, anonymous classes naming policy, and more in a deeply technical yet engaging manner
Check-out how Compose Hot Reload is implemented:
youtu.be/UebhKUdO2sQ?...
@Sellmair did an amazing job -- explaining dynamic classloading, DCEVM, continuous builds, Compose internals, anonymous classes naming policy, and more in a deeply technical yet engaging manner
But the thing I am most proud of is our release of Kotlin LSP along with VSC support: github.com/Kotlin/kotli...
Damn that was some action!
But the thing I am most proud of is our release of Kotlin LSP along with VSC support: github.com/Kotlin/kotli...
Damn that was some action!
I'd even say it might have an effect similar to deprecating String.capitalize(), but this time with a (hopefully) properly-named replacement
👉🏼 We need a name for the improved replacement function! What would you suggest as a name? (e.g. I'm a fan of `withTimeLimit`!)
I'd even say it might have an effect similar to deprecating String.capitalize(), but this time with a (hopefully) properly-named replacement
Now with Germany and Netherlands on the table!
Now with Germany and Netherlands on the table!
If you are eager to write something you are going to regret (if you are lucky, also be proud of) in 10 years, want to tinker with Kotlin and not afraid of dragons (also: performance, concurrency), drop me a line!
If you are eager to write something you are going to regret (if you are lucky, also be proud of) in 10 years, want to tinker with Kotlin and not afraid of dragons (also: performance, concurrency), drop me a line!
Does anybody else have this at all?
Does anybody else have this at all?
gist.github.com/qwwdfsad/b13...
gist.github.com/qwwdfsad/b13...