Zsolt Donca

/g/ spares no one

I need only one simple example to convince you that OOP patterns are scams, and Category Theory patterns are superior. In the OOP world, when you tell me something is a 'Visitor', you tell me nothing. So are you telling me that this code traverses some values and maybe even recursively calls itself? Well, f*cking thanks, Sherlock, you just literally described 90% of every OCaml project. Your words said nothing of value and wasted my time. However, when you tell me that something is 'Applicative', I immediately know: 1. THE EXACT NAMES OF FUNCTIONS TO USE. Yes, the abstraction is THAT precise. It's and+/pure in OCaml, and the Star Wars TIE Interceptor ship operator/pure in Haskell. 2. THE EXACT TYPES OF EVERY FUNCTION. 3. How to create values of that thing: use 'pure'. 4. How to compose values of that thing: use 'and+'. 5. The parallelism semantics attached to the composition. 6. What extra rules and laws those functions follow. 7. An entire library of 100 REUSABLE FUNCTIONS I can immediately benefit from with my value. 8. What other abstractions are implied: every Applicative is Functor, so by definition, I know what else I can use with my value. You said just one word — Applicative — and it singlehandedly absolutely f*cking destroyed entropy. I immediately know everything I need to know. A single word says more than an entire useless book.