3 ms·
My understanding of all these projects is that you have to change your style of coding / have more complex APIs, or they're just syntactic sugar over heavyweigh
by relics443 9y ago
My understanding of all these projects is that you have to change your style of coding / have more complex APIs, or they're just syntactic sugar over heavyweight threads.
What loom seems to offer is the best of both worlds; going back to writing simpler code (e.g. regular "blocking" io code) while scaling much better.
- SureshG 9y ago> have more complex APIs, or they're just syntactic sugar over heavyweight threads. I am pretty sure that's not the case with Kotlin coroutines :)
- _Codemonkeyism 9y ago"blocking" io code would be blocking. Every IO library would need to migrate to something non blocking. This might happen with some - currently some use Netty and NIO - but e.g. JDBC drivers are synchronous.
- relics443 9y agoI believe the article mentions making the java.io package aware of fibers.
- _Codemonkeyism 9y agoYes you're right, though it would be a miracle - I hope for it ! - if this can be done without changes to existing code.