ZIO VS Monix

If you have experience using Future, and are looking for an introduction to "Why ZIO?", then you might enjoy my talk, Upgrade Your Future. The talk contains a bit of getting started material, and you can keep an eye on zio.dev for more tutorials geared at users of Future and Akka.

Release notes: https://github.com/zio/zio/releases/tag/v2.0.0

The reason why I have banned ZLayers from our code was triggered by this: https://github.com/zio/zio/issues/5339

Coming from the Scala world this comment confuses me.

We know actors very well and we've had a popular and solid implementation in Akka for years.

But that hasn't mean that every other concurrency model has gone away. If anything with the advent of libraries like ZIO (http://zio.dev) we see concurrency being a hot space for interesting new takes and approaches.

zio.dev contains hundreds of pages of free content

Scala. With the functional effect systems, like Cats Effect or ZIO, you get superpowers.

Not only can write programs that are "async", but you also get easy retries (and other tricks), safe refactorability (because of its Pure FP nature), reliable and painless resource management and some other goodies like STM (Software transactional memory).

It's really that good.

https://www.youtube.com/watch?v=qgfCmQ-2tW0

https://zio.dev/

https://typelevel.org/cats-effect/

Define new? Isn't Zio new enough?

If you want to use Scala then I would use something like ZIO as it is the closest to an FP application framework.

> doing FP in Scala versus alternatives

I think Scala is the language most actual functional programming on this planet takes place these days. Be it just FP or pure FP.

I especially like pure FP in Scala. One can do that with Cats Effect (from the TypeLevel family of languages) or ZIO. They're both awesome, so check them out and pick what you'll like best.

https://typelevel.org/cats-effect/

https://zio.dev/

You don't even need to reach out to Scala 3 (still not as mature in its tooling support), you can have a great time with the latest Scala 2 (2.13).

> versus alternatives

I think of Scala as a opinionated take on ML and a module system that is tailored to JVM (and is seamlessly interoperable with Java) that just happens to have syntax heavy on braces/parentheses. Otherwise, what's not to like? :)

Monix exposes Observable with similar API. It has a stronger FP influence but there are more similarities than differences.

The Observer is a bit different, it returns Future[Ack] for built-in back-pressure. We can Continue / Stop synchronously or asynchronously.

cats-effect or monix or ZIO for Scala.