re: In praise of Vavr's Option VIEW POST


I like the library and really missing immutable persistent collection in Java: my only concern is the confusion that a different but homonymous class, like List, can create in a team.
On the other hand this is the price to pay if you want to write something interoperable with the existing API but that can change and enhance the original design.

Thanks for the nice write up.


Thanks for the kind words. In fact, I share your concern...but we've found that we can easily use multiple libraries like Vavr in parallel, we just decide on a per-component or per-microservice level which way to go.

As Vavr is really non-invasive, there is no actual risk.

Code of Conduct Report abuse