What is the state of Multiplatform currently? Is it worth trying to publish a Multiplatform library ...

# multiplatform

[CLOVIS]

What is the state of Multiplatform currently? Is it worth trying to publish a Multiplatform library now, before KLib comes?

[russhwolf]

Plenty of libraries already publishing. New klib stuff will presumably simplify things but nothing blocking you from putting something out now.

[darkmoon_uk]

The biggest problems I see facing Multiplatform at the moment are:
• Clash between K/N memory model and multi-threaded coroutines. This is being actively worked on and the situation is improving.
• Gradle Composite Builds and Multiplatform currently don't work properly together in IntelliJ IDE's - objects in the dependency source-sets aren't resolved even though they should be. For the workflow I want to adopt, where several multi-platform libaries get developed in parallel, Composite builds are idea, making this a rather annoying problem.

[darkmoon_uk]

That said; I have been pushing the adoption hard at work and it looks like we're reaching approval to use K/MP as a core part of our Client App strategy going forward - so I will have to find a way through these issues somehow 😅.

[darkmoon_uk]

I don't really see KLib as anything to wait for either; I expect Gradle to abstract this enough that the change will not be noticed for most use cases.