@lxsameer hey 😄

@hamid hey man

Some food for thought: https://pchiusano.github.io/2017-01-20/why-not-haskell.html

Paul Chiusano's book, Functional Programming in Scala is really good.

@beppu I agree!

loved the credit card example

@pesterhazy I'm only about 1/4th of the way through the book (so I haven't seen the credit card stuff yet), but an early big revelation for me was that exceptions weren't functional. The monadic error handling alternative was something I really wanted to know more about.

I've come to accept exceptions

they're actually not that bad

@pesterhazy I went back to look for the credit card stuff, and I saw it was in the first chapter. I had totally forgotten about it!

I've tried using monads in clojure to return value-or-failure, but it's messy

When I get a chance, I'm looking to give this library a spin for monadic error handling: https://github.com/adambard/failjure

that's what I used!

adam has a great blog post about that too

my use case wasn't right though

think credit card processor failure in an order process

exceptions are actually a good fit for that 🙂

I'm gonna have to play with it myself to convince myself one way or the other.

https://adambard.com/blog/introducing-failjure/

I find myself using it for contained situations, but it’s a bit inconvenient to thread through your entire application

definitely not a replacement for exceptions

Exceptions are basically implicitly-wrapped Result-type returns

Java doesn't quite handle them that way - you can't lift an exception-throwing function into a Result-returning function reliably in Java, since you can't parameterize exception types for functions. But I'm guessing Scala might.