what is the specific technical limitation that pre...
# multiplatform
k
what is the specific technical limitation that prevents multiple MPP frameworks in an iOS app?
b
There's a runtime assertion that fires when you load the 2 frameworks about not allowing 2 K/N runtimes to run
k
thank you!
though I am still curious what the actual limitation is
i see the "closed world" compilation model explanation.
b
i think at the moment, it has more to do with the vision and less about technical limits, but now that everything is designed this way, it may take work to get out of that world, if JB is so inclined
k
it definitely adds a lot of overhead for organizations that want to invest in Kotlin MPP
creating and maintaining each of these "umbrella" projects for each app
b
we're working around it by using "export" thing here: https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html
p
There is overhead for sure, but I wouldn’t say a lot. I have my common code broken out into subprojects and have a buildscript in their root to combine them into a single MPP project: https://github.com/pardom/lambda-news/blob/master/common/build.gradle.kts
k
a buildscript is definitely helpful
my gradle fu isn't particularly strong
o
Generally, we suggest modularisation on klib level and single framework at the end
k
will have to find the best practice for doing so