2 ms·
I came from an imperative background so it didn't bother me so much. I agree it makes people suck at FP. Least there's good free work like "How to Design Progra
by nickpsecurity 11y ago
I came from an imperative background so it didn't bother me so much. I agree it makes people suck at FP. Least there's good free work like "How to Design Programs" with the Racket tools. Should give them a nice boost.
However, there's lots of ways to scale. FP is better at it but not necessary. It's easier for a decent imperative programmer to learn to scalable concurrency than to learn FP. So, path of least resistance & backward compatible means that non-FP approaches should get most traction. That's what we see in practice.
Good news is that your point got many interested in making an attempt and led to more FP developers + languages. I even saw a case study of a company in finance using Haskell for production due to concise, correct, and concurrent properties. Plenty potential here.