4 ms·
One of the main authors of ZIO (another effect runtime in Scala) gave a talk about ZIO + Loom. https://youtu.be/ygOmwze5ETk https://youtu.be/ygOmwze5ETk For s
by doikor 3y ago
One of the main authors of ZIO (another effect runtime in Scala) gave a talk about ZIO + Loom.
https://youtu.be/ygOmwze5ETk https://youtu.be/ygOmwze5ETk
For some use cases there seems to be a performance advantage for using Loom if the library properly supports Loom. (Mainly gain it from using plain old boring blocking IO instead of async NIO stuff which has overhead. https://youtu.be/ygOmwze5ETk?t=2396 https://youtu.be/ygOmwze5ETk?t=2396)
And at least according to JDG cats-effect is heavily tied down to their Async means they can't as easily work around the async overhead as ZIO can. Don't know if this is actually true or not. Would need input from actual cats-effect maintainers on this.
- flylikeabanana 3y agoDaniel Spiewak has posted a perspective before. The TL;DR is that Loom makes the implementation of CE/ZIO more straightforward, but it probably won't replace the effect systems themselves since they offer a lot more than just "light threads": https://www.reddit.com/r/scala/comments/sa927v/comment/htsoydn/ https://www.reddit.com/r/scala/comments/sa927v/comment/htsoy...
- dkarl 3y agoFWIW, the cats/zio split has historically seen a lot of contentiousness and hostile feelings both ways, for reasons unrelated to their technical differences, so I would take anything negative one side says about the other with a bigger dose of skepticism than usual.