Loom brings more than just performance, which as you rightly point out is probably already addressed by ZIO/Monix/Kotlin (or even improved). First there’s the syntactic changes, which impact the readability of the code. Some might consider code written in procedural style to be more readable, at least in some scenarios.

Second, there’s the problem of lost context, especially when reporting exceptions. Here, although ZIO & cats-effect 3 have improved a lot on the status quo, we still don’t get the same experience as with synchronous code & “normal” stack traces.

Finally, both ZIO & cats-effect are quite viral, while Loom might blend more seamlessly with other libraries and frameworks that you might use in your code.

--

--

--

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Warski

Adam Warski

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

More from Medium

Differences between Abstract Classes and Interfaces

LRU Cache Behaviour Implementation in Scala

N Queens Problem

Writing Robust Hoon — A Guide To Urbit Unit Testing