|
|
|
|
|
by wbillingsley
1382 days ago
|
|
It seems (to me) less complex to have that as "just a library". In most of my little projects, I don't use ZIO, I just have a tiny library I wrote years ago that lets me write stuff that works ok whether it's a Future[Seq] or a Seq[Future] or a Future[Seq[Future[Seq]]] underneath.
https://github.com/wbillingsley/handy If ZIO (or some other choice) were baked into the language, I'd be using their choice of async libnrary for everything whether I want to or not. And I wouldn't be able to switch to the new-shiny-and-exciting-thing that comes out when I want to explore it because "sorry, X was what the designers chose when the language was written, so X it must be". In Scala, I can use my little thing I'm familiar with, or I can try out ZIO, or Cats-Effect, or Akka Streams (before the licence change). I get to explore concepts very quickly and very easily without having to shift languages and learn a new set of build tools and syntax at the same time. |
|