What’s so great about functional programming anyway?
I read the whole thing waiting for the aha-erlebnis which never came. I&#x27;m a full stack JS&#x2F;TS engineer with a decade of experience. I expected this article to be written for someone like me. It didn&#x27;t click, even though I already love and use functional aspects like immutability and pure functions. I feel like it&#x27;s the whole new set of terminology that puts me off (and I&#x27;m talking about `scan` and `Task`, not even `Functor` or `Monad`). I have confidence I can learn and apply this in a few weeks, but I can&#x27;t realistically expect junior&#x2F;medior devs to quickly onboard into a codebase like that.<p>Maybe I&#x27;m biased against &quot;true&quot; functional programming because I&#x27;ve been on Clojure and Scala projects in the past (as a backend dev) and both experiences have been good for my personal&#x2F;professional development, but a shitshow in terms of long-term project maintenance caused by the enormous learning curve for onboarding devs. The article talks about how great it is for confidently refactoring code (which I bet is true) but doesn&#x27;t talk about getting people to understand the code in the first place (which is still a requirement before you can do any kind of refactoring).<p>My only hope is for ECMAScript (or maybe TypeScript) to introduce these OK&#x2F;Err&#x2F;Maybe&#x2F;Task concepts as a language feature, in a way which befits the language rather than trying to be &quot;complete&quot; about it. We don&#x27;t need the full spectrum of tools, just a handful.