Post #2637540

@cocoafrog@hachyderm.io @ktoso@mastodon.social @ole@chaos.social Absolutely; it works well for performance. This particular issue was deadlock (*), either due to a Task exiting when it shouldn't, or a Task not honoring cancellation, and not exiting when it should. In Kotlin, coroutines generally can be debugged similarly to threads. In Swift, when things go wrong, there's not really any way to inspect the system. (*) yes, I'm playing loose with the meaning of "deadlock" but the app stops doing what it should.