📢 Kotlin 2.4.0 is out! Here are some of the highlights:
✅ Language: Stable context parameters, explicit backing fields, and multiple features for annotation use-site targets.
✅ Standard library: Stabilized support for the UUID API and support for checking sorted order.
✅ Kotlin/JVM: Support for Java 26 and annotations in metadata enabled by default.
✅ Kotlin/Native: Support for Swift packages as dependencies, updates on Swift export, and the CMS GC enabled by default.
✅ Kotlin/Wasm: Incremental compilation enabled by default and support for WebAssembly Component Model.
✅ Kotlin/JS: Support for value class export and ES2015 features in JS code inlining.
✅ Gradle: Compatibility with Gradle 9.5.0.
✅ Maven: Automatic alignment between Java and JVM target versions.
✅ Kotlin compiler: More consistent inline function behavior during .klib compilation.
Learn more: https://t.co/8cT1Jicklk
🚀 One of the biggest announcements at #KotlinConf26 was the Kotlin Toolchain.
It’s a unified entry point for:
⚡ Creating apps
⚡ Building and testing
⚡ Formatting
⚡ Doc generation
⚡ AI agent integrations
Available today for JVM and KMP projects.
https://t.co/gk8VQEtecp
If anyone is still interested in sweet-spi, a.k.a. my take on SPI in KMP, feel free to check the project status update at the link below.
TL;DR: KSP will be replaced by Kotlin Compiler Plugin... When I have more time...
https://t.co/y8zAaN1p6g
📢 Kotlin 2.4.0-RC is out! Here are some of the highlights:
✅ Language: Stable context parameters, explicit backing fields, and multiple features for annotation use-site targets.
✅ Standard library: Stable UUIDs and support for checking sorted order.
✅ Kotlin/JVM: Support for Java 26 and annotations in metadata enabled by default.
✅ Kotlin/Native: Support for Swift packages as dependencies, updates on Swift export, and default CMS GC.
✅ Kotlin/Wasm: Incremental compilation enabled by default and support for WebAssembly Component Model.
✅ Kotlin/JS: Support for value class export and ES2015 features in JS code inlining.
✅ Gradle: Compatibility with Gradle 9.5.0.
✅ Maven: Automatic alignment between Java and JVM target versions.
✅ Kotlin compiler: More consistent inline function behavior during .klib compilation.
Try it out: https://t.co/BaJwyYDrGD
Documentation tooling in Kotlin has been an afterthought for too long.
New KEEP proposes to change that
Kotlin Documentation Model - a stable, machine-readable representation of your module's KDoc and API surface, integrated into the Kotlin Build Tools!
https://t.co/7gL8PwU7ME
📢 Kotlin 2.4.0-Beta2 is out! Here are some of the highlights:
✅ Language: Stable context parameters, explicit backing fields, and multiple features for annotation use-site targets.
✅ Standard library: Stable UUIDs and support for checking sorted order.
✅ Kotlin/JVM: Support for Java 26 and annotations in metadata enabled by default.
✅ Kotlin/Native: Support for Swift packages as dependencies, updates on Swift export, and default CMS GC.
✅ Kotlin/Wasm: Incremental compilation enabled by default and support for WebAssembly Component Model.
✅ Kotlin/JS: Support for value class export and ES2015 features in JS code inlining.
✅ Gradle: Compatibility with Gradle 9.4.1.
✅ Maven: Automatic alignment between Java and JVM target versions.
✅ Kotlin compiler: More consistent inline function behavior during .klib compilation.
Try it out: https://t.co/gv4CerPHBm
@vergauwen_simon True, supporting every use case in a logging library is almost impossible, there are a lot of sacrifices along the way. So, yes, maybe, we don’t need standard logging library at all? :)
Why does everyone wants to create a logging library?
I mean, I’ve seen more than 50 Kotlin libraries, most of them doing roughly the same…
There is even four libraries with ~+1000 stars!
And still, every month in a while one more is created
And still, there is no default choice
@sur3shg I’m curious, why do you think that logging should be first party?
Not every popular/modern language/ecosystem has first party logging API, or, even could have one, but no one will use it (hello Java)
See for yourself: https://t.co/wqP8SM345R
Should we (as a community) do something about it?
Of course, I’m not against creating new libraries, but do you think that all this enthusiasm could be redirected to other, less developed categories?
🚀cryptography-kotlin 0.6.0 is here🚀
- More algorithms, including EdDSA and ChaChaPoly
- New website with a lot of new content
- Improved CryptoKit/Swift/Xcode compatibility
- New API to get a public key from a private key
- JWK encoding in all providers
https://t.co/NxIf9rmHr3
Thanks to everyone who uses and contributes to the project - it truly means a lot ❤️
If you or your company rely on the library, consider supporting its development. This helps keep it maintained and evolving.
https://t.co/UFYxg7whll
But the most exciting part isn’t the release itself, it’s the people who use and contribute to the library!
Recently, I collected statistics on algorithm usage and was impressed by the number of projects and the variety of use cases!
https://t.co/ODhbVhBXw5