Viewing a single comment thread. View all comments

cesium-sandwich t1_iy6sqa6 wrote

I didn't read the article, but do they address how immutability goes against the concept of caching? Also, FP relies pretty heavily on garbage collection, which has been one of my reasons for avoiding some FP paradigms in my work...

−6

msbic t1_iy89bhd wrote

Garbage collection is fine for most scenarios. My company uses a garbage collection language for a trading system. Not without some trickery, but nevertheless.

1

cesium-sandwich t1_iy8eqnb wrote

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.

0