4 ms·
> The consequence is that the whole ecosystem is split in two parts! Which it might continue to be. As Kotlin needs to support other backends than just the JVM
by kasperni 6y ago
> The consequence is that the whole ecosystem is split in two parts!
Which it might continue to be. As Kotlin needs to support other backends than just the JVM.
- sgt 6y agoWhy does it absolutely need to? I thought the purpose of Kotlin was to primarily be a JVM language.
- kasperni 6y agoIt started out with just Kotlin/JVM. But now you also have Kotlin/Native and Kotlin/JS. Being multi-platformed has some drawbacks, for example, that it can be difficult to expose certain abstractions that are only supported on a subset of the platforms.
- sgt 6y agoThanks, I didn't know that. It seems like that would slow down the project a bit.
- The_rationalist 6y agoKotlin can to lower it's IR to platform specifically intrinsics and have platform exclusive features to an extent. E.g inline classes are currently only available on the JVM
- kasperni 6y ago> Kotlin can to lower it's IR to platform specifically intrinsics and have platform exclusive features to an extent. As pointed out elsewhere this won't really help you in any way in this situation.