Kotlin Weekly

Livestream: UI Freezes in JetBrains IDE Plugins and How to Avoid Them | The JetBrains Platform Blog Join Yuriy Artamonov, an IntelliJ Platform expert, for a livestream on preventing UI freezes in JetBrains IDE plugins.

If you build plugins for @jetbrains.com IDEs, UI freezes are among the fastest ways to ruin the UX.

My colleague Yuriy will host a livestream on why they happen, how plugin code can accidentally block the UI thread, and how to avoid it.

Details 👇
blog.jetbrains.com/platform/202...

Kotlin Weekly #501 (Not Implemented) has just been published! - mailchi.mp/kotlinweekly...

Curious to know what @jetbrains.com Developer Advocates do on Bluesky?

Here's a list you should use 👇

bsky.app/profile/did:...

Kotlin Weekly #500 (Internal Server Error) has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #499 has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #498 has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #497 has just been published! - mailchi.mp/kotlinweekly...

Shared Internals: Kotlin's New Proposal for Cross-Module Visibility Explore Kotlin's KEEP proposal for shared internal visibility. Learn how this new modifier enables cross-module visibility control while maintaining encapsulation from external consumers.

Thanks @androidweekly.bsky.social and @kotlinweekly.bsky.social for featuring my recent article, 'Shared Internals: Kotlin's New Proposal for Cross-Module Visibility'.

The KEEP proposal about the new visibility level sits between internal and public.

doveletter.skydoves.me/preview/arti...

Thanks so much to @kotlinweekly.bsky.social for including my video about Kotlin 2.3's Explicit Backing Fields in this week's issue! If you're a #Kotlin developer, go follow them for weekly updates with all the latest Kotlin news.

WAT

We're here at #FOSDEM! Visit the Kotlin Community Stand in Building K, level 1 (group A).

Kotlin Weekly #496 has just been published! - mailchi.mp/kotlinweekly...

Joining the #FOSDEM today! Ping us if you want to meet for a coffee and discuss Kotlin.

Kotlin Weekly #495 has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #494 has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #493 has just been published! - mailchi.mp/kotlinweekly...

Kotlin Weekly #492 has just been published! - mailchi.mp/kotlinweekly...

Is this an honest question or just more of the previous reductionism and condescension?

In any case, among others, we use Iterative Consensus. Running the same dataset through multiple models and prompt structures. Consistent results provide a high statistical confidence level.

Not really. We don't always use the same identifier for a contributor. It could be a first name, a full name, a nickname, or no name at all. Contributors write in corporate blogs, private blogs, and Reddit. This is not something you can track manually.

Kotlin Weekly #491 has just been published! - mailchi.mp/kotlinweekly...

A good example of AI not doing its job is not having @johnoreilly.dev here. John, you should have been in the top 5.

If you want to follow them:

@dmcg123.bsky.social
@skydoves.bsky.social
@typealias.com
@sam-cooper.bsky.social
@amanda-hinchman.bsky.social
@vadim-briliantov.bsky.social
@arnogiu.bsky.social
@zacsweers.dev
@darrylbayliss.bsky.social

List of the top contributors to the Kotlin Weekly in 2025 (this required a few iterations with AI to get it right):

We used AI to scan our 2025 archives and highlight the most relevant Kotlin moments of the year. We then cross-checked the results with a second AI agent to validate their accuracy, without evaluating the editorial relevance of the content.

This is what we got 👇

@kotlinweekly.bsky.social @eenriquelopez.bsky.social - Thank you for sharing our work on the migration from Android apps to KMP!