Statement on #Vavr's Future
https://danieldietrich.dev/blog/2024/06/06/statement-on-vavrs-future/
Statement on Vavr’s Future
@SusanPotter @routis the question was about #java+functional idioms... So #Kotlin is out of context 😅
I love kotlin, I'm even GDE for this specialty, but if the requirement is Java, then we should not advertise for it. #KotlinFatigue
And yes, #VAVR is old and not maintained a lot... But it still exists and works as a lib😇
#vavr is / was? an awesome library. Offers Try, Either, Validation, and immutable collections and many more.
I don't think though that it is being actively maintained.
If you want to learn functional programming I suggest to consider #kotlin
Language has great support for immutable data structures (data classes, immutable collections) and in addition there is #arrow-kt library.
The later is a modern and kotlin idiomatic FP library.
@SusanPotter I used #VAVR a lot before switching to #Kotlin.
Inspired by Scala, every useful functional structure should be available
💡Java Exceptions are not my best friend. When I found replacement for it in Either my approach to coding changed drastically. In below post I wanted to share with you my thoughts on why in code it is better to use Etiher approach, and leave Java exceptions for JVM internals.
https://dev.to/michaltalaga/my-problem-with-java-exceptions-and-remedy-for-it-either-40g9
#java #Java17 #functional #spring #vavr
Using pattern matching with sealed interfaces and the vavr Either type to give a much cleaner way to handle errors in a Spring Rest controller https://softwaremill.com/functional-error-handling-with-java-17/