Remember, we're simply comparing FP to imperative programming. I'm simply not convinced that FP is easier to learn than imperative programming for the vast majority of newcomers, and that's what I'm arguing here.
I think because of the limitations of FP it’s much easier for new programmers to reason about programs and honestly, learn to program.
New developers don’t have to micromanage the computer, the way that the would with an imperative lang.
For example, SQL isn’t FP, but think about the number of business analysts whose lives would be more difficult if the had to write imperative programs to fetch data from some sort of data store.
I think what in comes down to is simple vs easy. Imperative programming in the very very beginning is easy, buts not simple.
Because there’s all this implicit state in your program, as the program grows it becomes very very complex. It’s no longer simple.
There’s this really great talk about this idea by rich hickey, the creator of clojure, that dives into this in detail.
FP is supposedly easier to use in the long run but it’s definitely harder to pick up.
Imperative is the opposite since it’s analogous to writing out a list of things you want the computer to do - a concept even the uneducated can understand.
functions, algebra, assignment, etc.
All functional programing languages, have ergonomics in their syntax and semantics. around referential transparency and immutable data structures, there's nothing in there about Monads or Functors or Hindley–Milner type systems.
Languages like Haskell do benefit from having that kind of experience, however, langs like, OCaml, Erlang, Elixir, Gleam, Racket, Clojure, Standard ML.... and the list goes on, doesn't require that kind of education.
(Antidotally, I find FP langs much easier to reason about and I have a background in the humanities. I just don't buy the advanced math argument.)