3 ms·
It's kind of odd that JetBrains chose async/await for Kotlin considering the JVM is going towards the Go approach for virtual threads. I guess they had to since
by vips7L 5y ago
It's kind of odd that JetBrains chose async/await for Kotlin considering the JVM is going towards the Go approach for virtual threads. I guess they had to since they wanted to support android/js?
- pjmlp 5y agoThe decision happened before Loom came to be. It is yet another example of impedance mismatch from guest languages, when the platform moves into another direction. The platform language gets the true way, while the guest languages get the hard decision how to combine multiple approaches, and libraries that only use the new platform APIs.
- SureshG 5y agoYeah that decision make sense for multi platform. Suspending functions will work on JS and Kotlin Native.
- jayd16 5y agoIt makes sense for UI patterns and any pattern where you need to bind to a specific OS thread.