Don't think it's practical/good to make people learn >>=, <$>, <*>, <|, <|* to decode JSON.
Alternative pragmatism:
Conversation
My concern is about empathy and strategy when working with a team of traditional engnrs. Forcing alien concepts on others has cost.
1
1
Can lead to animosity within teams, greater recruiting and onboarding challenges. Not saying it's never worth it. Just expensive.
1
Absolutely. But there’s a way to ease these onto people. Not enough of this is taught as patterns; too much category theory
1
Replying to
Yeah. The key thing is: they have to *ask* first, and the initial answer has to be digestible in a sitting. The next one, too, etc.
Replying to
the risk, though, is you present a Monadic parser, then get shouted down and have to wrap it in an imperative interface.
Replying to
RAC has it good: It’s OO but it uses the opportunity to have a Monadic core over an approachable interface. *
1
RAC's more approachable, for sure, but it still causes a lot of consternation in industry engineers. We can improve. Trying…
2
Show replies
Replying to
*But it isn’t a monad at heart. JSON parsing, as in the OP, starts out Monadic and has to be diluted to be “approachable”