&gt; as a paradigm, FP solves problems that only experienced programmers realize they have<p>This is exactly what I&#x27;ve been saying... and it&#x27;s the essence of the &quot;FP non-adoption problem.&quot; I came to FP because I became frustrated with classes of bugs that appeared over and over again in OO (Ruby, in my case) but which seem to plague FP code much less. In essence, I came to reduce labor&#x2F;increase productivity; it&#x27;s &quot;laziness&#x2F;impatience&#x2F;hubris&quot; all over again.<p>One indicator that I was &quot;naturally&quot; coming to FP is that I noticed I was writing Ruby code in a very functional style. I say &quot;naturally&quot; because 1) it made it easier to test 2) it reduced spaghetti code and dependencies 3) it made it more modular 4) it reduced side effects and bug generation. And all of these worked together to just make better code, period.<p>Then I came across Elixir (<a href="http:&#x2F;&#x2F;elixir-lang.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;elixir-lang.org&#x2F;</a>) and lo and behold, now I can&#x27;t wait to find work in this shiny new FP language.<p>If most people in a career came to prefer a certain paradigm after 10-20 years in that career, shouldn&#x27;t everyone in that career be taking a serious look at it?