I'm excited about #Scala3. I'm excited about Loom. I think that Scala 3 running on Loom will be the closest I'll get to a "gamechanger" to my everyday work in the next 10-15 years.
-
-
Replying to @propensive
Interestingly,
@djspiewak said that Loom is not ambitious enough and it's authors claim it's not possible to do things that Cats Effect, Monix and ZIO are already doing. It might still prove itself useful in Scala effect systems if low level primitives are exposed in the API.1 reply 1 retweet 7 likes -
Replying to @rafal_krzewski @propensive
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?
2 replies 0 retweets 5 likes -
Replying to @djspiewak @rafal_krzewski
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.
2 replies 0 retweets 2 likes -
Replying to @propensive @rafal_krzewski
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.
2 replies 0 retweets 6 likes -
Replying to @djspiewak @rafal_krzewski
Ok, I should. My dependencyphobia is mostly what's put me off.
1 reply 0 retweets 1 like -
Replying to @propensive @rafal_krzewski
I definitely get dependencyphobia, but the way I think about is this: every dependency you take on is a vote of confidence in the maintainers of that dependency to keep it alive, remain compatible, etc. Not all dependencies are created equal, and you judge by trust.
1 reply 0 retweets 8 likes
That's a nice philosophy in many ways, but I don't like that it places such a burden of proof on OSS developers. I think too many projects don't get traction because the maintenance is too hard. But my problem is also my fault, here... Hence why I'm trying to fix it, too...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.