FunctionalProgramming
Post #7983 · source on Telegram
Learning Curve Asymmetry: FP to Imperative vs Imperative to FP
Description
Two-panel meme using the Filthy Frank cigarettes-up-the-nose template. Left panel, captioned 'Functional Programmer Learning An Imperative Programming Language': a grinning man with glasses gives a thumbs up with two cigarettes stuck in his nostrils - goofy, but happy and in control. Right panel, captioned 'Imperative Programmer Learning A Functional Programming Language': the same man screams in despair with a handgun in his mouth. The meme asserts the asymmetry of paradigm switching: going from pure functional concepts (immutability, monads, recursion) to mutable imperative code feels trivially permissive, while imperative programmers confronting functors, type classes, and the absence of loops and mutation experience existential dread
More like this
More like this in FunctionalProgramming →
Use J and K for navigation
Comments
3Comment deleted
Going FP to imperative just means unlearning discipline; going the other way, the compiler rejects your entire mental model with a 40-line type error
The code has no side effects; the tutorial caused several.
thing is, that functional languages allow to do imperative style, so the func-devs basically already aware of the other side. https://news.ycombinator.com/item?id=14551168 here is a good discussion Comment deleted