@dandi8@JackbyDev Most of the criticism in the article talks about side-effects using a far stricter (and imo more useful) definition than Martin did.
I tend to agree, and would avoid both side-effects and writing code like Martin. However this book targets the mainstream, and afaik the mainstream hasn’t yet accepted the new definition of side-effect.
Martin has since embraced FP more than the mainstream. So he’s somehow both ahead of and behind the curve.
This is a good point. A perfect litmus test for this is whether people consider logging a side effect. With the strict, functional definition it is. With the loose, practical definition it is not.
@dandi8 @JackbyDev Most of the criticism in the article talks about side-effects using a far stricter (and imo more useful) definition than Martin did.
I tend to agree, and would avoid both side-effects and writing code like Martin. However this book targets the mainstream, and afaik the mainstream hasn’t yet accepted the new definition of side-effect.
Martin has since embraced FP more than the mainstream. So he’s somehow both ahead of and behind the curve.
This is a good point. A perfect litmus test for this is whether people consider logging a side effect. With the strict, functional definition it is. With the loose, practical definition it is not.
Any examples of the claim that he’s embraced FP more?
Last I saw, he was making wild, baseless assertions about FP concepts like monoids and monads on Twitter.
@expr this is from 10 years ago https://youtu.be/7Zlp9rKHGD4