@withoutclass You probably already know that but just in case: in order to understand the kind of code that Arrow (and FP in general) encourages, you need to spend a large amount of time studying not just Arrow but a lot of peripheral concepts. This is a big investment, one that people who are fluent in this kind of programming tend to forget or gloss over. If you don't quite understand the push back, picture yourself five years ago and staring at Arrow-like code: what would you have thought if someone on your team promoted this kind of programming?

I completely agree. I am actually very new to any FP at all. I would like to learn because I think it is going to provide a great benefit to myself and my team. My team has been moving towards using sealed classes for Rx and return types in general, and I saw a good opportunity with

Either

to reduce how many extra classes I was writing, as well as begin to bring some small FP concepts into our code.