Jon Pretty

I'm curious, Jon, as to what about Loom you would consider to be a game changer for your everyday work? Or, more relevantly, what does it change that you can't already achieve today?

I'm mostly looking forward to the reduction in obfuscation that comes with async APIs. I used to write async code using plain Threads because I didn't worry about scalability, and it was easier to understand. And a decade later, it kind of still is.

I think what I'm getting at is I don't really see that there's any obfuscation any longer. These frameworks really solve the problem.

Ok, I should. My dependencyphobia is mostly what's put me off.

It really doesn't. That's kind of my whole complaint about Loom. Literally the only *benefit* it brings to frameworks like Cats Effect is the ability to make some(!) hard-blocking on the compute pool a little less cataclysmic for users.

I'm quite sympathetic to that, though, since I've wasted days of my life on compute pool exhaustion...

Right, and Loom will make that *better*, but it won't eliminate it. Plenty of blocking things will still hard-block carrier threads unavoidably (e.g. new URL(...), or any file IO).