Fully agree that libraries should convey their compatibility within the version. The proposed schema is still semver compliant, so it's gonna be OK.
Just to check: I was not proposing that every version should be aligned, just the notation should be consistent (and the semantics of each part)
The Kotlin ecosystem might not choose a strict 'SemVer' notation (and it's gonna be fine!)
blog.sellmair.io/the-kotlin-e...
Compose Hot Reload is now stable and bundled with Compose Multiplatform since v.1.10.0! 🎉
This deep dive by @sellmair.dev and Azat Abdullin walks through the engineering behind Compose Hot Reload and how it works under the hood.
For the curious among you 👀
https://kotl.in/hotreload100
I am working on a proposal on making Kotlin's ecosystem versioning more consistent (at least for JetBrains projects at first). It sparked this nice blog post from @mbonnin.net . I'll respond on blog.sellmair.io soon 🔜
mbonnin.net/2026-01-16-s...
Compose Hot Reload 1.1.0-alpha03 just released, and it's pretty hot. 🔥
github.com/JetBrains/co...
- New, more advanced re-initialisation for statistics ↪️
- Up to 10x reload speeds by default 🏃🏽♀️
- Significantly reduced runtime memory usage 💾
You not using hot reload? 😥
So, today I found out about a secret, unsafe, internal property that makes Hot Reload waaaay faster. Like lightning fast. Even in a real project, not just with Hello World.
We're currently discussing if y'all are ready for this yet - we'll probably add it to guidance later.
What tools did you use for your AI workflow?
We're doing an AMA on /r/Kotlin on December 11th! Prepare your questions, mark your calendars, and join us there in 2 weeks!
www.reddit.com/r/Kotlin/
If you want to talk to our team, feel free to join the
Kotlin Ecosystem AMA on Dec 11, 15:00–19:00 CET on r/kotlin! See you there. 👋
It was such an amazing and fun project. I hope others might enjoy it as much as I did, but it's time for me to turn my head towards other problems and projects that we have in Kotlin.
However, while looking almost nostalgically at the project, I would like to announce that I transferred the ownership and maintenance of 'Compose Hot Reload' to dedicated teams at JetBrains, and I have found other people who will drive the project forward 🥹
We even have almost all features and changes ready for a 1.1 release. The first alpha is available, and we encourage you to try it out! 🤙
iOS hot reload has a proof of concept, and we hope to find enough time to productize it now 📲
"It should be easily doable to build a stateful hot reload" - silly me, almost one year ago.
After one year of hard work and many people involved, we can finally commit to the user experience and call it done (as in 1.0.0) 🔥
github.com/JetBrains/co...
🧵 What's next?
Package with a ‘Gradle’ adhesive
Ahhhh so that's why it's called the Gradle Wrapper?
Thanks for sharing, I can totally see why some people would not want to attend in this case 😓
Hey, I am just a curious listener without knowledge about Orlando: is the city known for being hostile towards said group?
Say hello to Compose Hot Reload 1.1 🔥
Please give it a try and provide feedback:
github.com/JetBrains/co...
☕️ JBR 25 support
⚡️ Recompilation Speed optimizations
😎 New visuals, New DevTools UX
📦 Faster, more lightweight protocol under the hood
We released Compose Hot Reload 1.0.0-rc01 🎆
What started as a happy accident was promised to be pushed towards stability as quickly as possible, allowing you to rely on a stable user experience.
github.com/JetBrains/co...
I am also talking about the behavior of updating dependencies the second they are released. It's culture now in Android Dev. I once saw a project utterly frustrated because a Kotlin update broke their workflow. Maintainers were quite loud, but refused to downgrade. Compatibility requires patience
But do you really need to be on the alpha, betas, or today releases to fix tech debt? Look at any public project and see the pre release usages. It's not healthy!
I said it once, I'll say it again:
You might think you're doing your project a favor by always upgrading to the latest AGP version.
What you do instead is break the project for everyone who has not downloaded the latest IDE.
This is pain
Casey Muratori pretty much sums up how I feel about LLMs for coding:
"The AI will always be useless for me. I physically can't get what I want from programming when AI is involved, because what it is doing is robbing me of the experience that I wanted to have and the knowledge that I wanted to get"
Say hello to hot reloading compose resources, supported from CMP 1.10.0-alpha01 🔥
Initially requested by @zsmb.co and @rakhman.info
Thanks to Nikita Lipsky 😇
Can kotlinx.coroutines outperform the GPU 🤯?
Watch me getting humbled while trying to find out...
www.youtube.com/watch?v=JCOS...
I hope you enjoy my journey. I learnt a lot and had plenty of fun! 🤪
www.youtube.com/watch?v=JCOS...
Let me tell you! It's a rollercoaster; I did not expect some of the things that happened, but I learned a few things. I thought it would be a quick benchmark and a recording, but I spent much more time here. Will record the results soon!
Are you okay with being mentioned in the video?
Benchmarking in progress, recording video today 😎
Oh, I did not expect to have so much fun building the IDE tooling/integration for Compose Hot Reload 😍
See the small floating toolbar when a session is present, even allowing you to reset your UI state!
Next video: Benchmarking! Would you be interested in sharing your code for comparison? The shader should be really fast, but I did not measure it!
