> We've decided to postpone... [improving] usab...

# kotlin-roadmap

[serebit]

We've decided to postpone... [improving] usability of multi-threaded coroutines library for Kotlin/Native

Why was this postponed? Looking at the results of the multiplatform survey, the top mentioned pain point of multiplatform is the strict memory model of Kotlin/Native and the inability to write concurrent code like in Kotlin/JVM, so it seems odd to me that this would be pushed back.

[serebit]

I hope it wasn't pushed back because of the appearance of Apple ARM systems 😛

[Zach Klippenstein (he/him) [MOD]]

I would expect this to be deprioritized in favor of building out the new memory model, which makes this a non-issue, but that wasn’t a new thing so I’m also curious.

[louiscad]

I'm 100% sure it's because the new memory model prototyping got top priority, and it will render that usability issue obsolete once it's ready to use.

[etolstoy]

The first step of working on this item was basically a technical research (like mostly in any other item on the roadmap). We didn’t find any good ways to both improve the usability over the current level and keep the maintenance in control.

Our current approach to this pain point is to redesign and implement the K/N memory model, which continues to stay on the roadmap and be the top priority for the K/N team.