Yeah I can see FP working really well for fintech.. in fact, it being pretty vital.
Mutable state is exponentially more risky when there's literal money on the line.. and it's worth burning cycles to ensure consistency and accountability.

My background is in games which has different incentives/constraints.
Just skimmed the article and as I suspected, it addresses neither of my questions.

Appreciate the response, and lol at the haskellers downvoting my question.

FP/Haskell has been the "future" of programming for over 30 years now, but in the majority of popular use cases, it turned out to be C/C++/C#/Rust/Javascript.
Not exactly the cold fusion of computer science, but not the iphone either.