Monads and Macros
johndcook.com · 534 words · saved by 1 readers
Monads and macros have an almost gnostic mystique about them. Why is that? Why does hardly anyone use both?
There are two techniques in software development that have an almost gnostic mystique about them: monads and macros . Pride and pragmatism As with everything people do, monads and macros are used with mixed motives, for pride and for pragmatism. As for pride , monads and macros have just the right barrier to entry: high enough to keep out most programmers, but not so high as to be unsurmountable with a reasonable amount of effort. They’re challenging to learn, but not so challenging that you can’t show off what you’ve learned to a wide audience. As for pragmatism , both monad
related reading
- how I think when I think about programming - alice mazalicemaz.com
- Macros - The Rust Programming Languageweb.mit.edu
- What is a Monad?lukechampine.com
- Weird Languagespaulgraham.com
- Abstraction, intuition, and the “monad tutorial fallacy” | blog :: Brent -> [String]byorgey.wordpress.com
- Good examples of Clojure macros usage which demonstrate advantages of the language over the mainstream? - Stack Overflowstackoverflow.com
- Monoids without tears | F# for fun and profitfsharpforfunandprofit.com
- You Can Choose Tools That Make You Happyborretti.me
- How to write complex softwaregrantslatton.com
- HiPhish's Workshophiphish.github.io
- Things unlearnedscattered-thoughts.net
- Repeat yourself, do more than one thing, and... — programming is terribleprogrammingisterrible.com