Functional programming isn’t how people think, and it isn’t how computers work. Therefore it’s a bad way for the two to communicate.
Unsurprisingly when I learned functional programming I found that it was a great match for the way I think, or at least the big picture way I approach programming. I doubt it's how all programmers think, but it's definitely the way I do.
That the programming paradigm that's used primarily by a small number of people who are into mathematical purity and is generally regarded as hard to wrap your head around, isn't how people think?
That the programming paradigm that takes so hard to not expose concepts like RAM or a program counter isn't how computers think?
Or that the combination of these makes it unsuitable for communication between the two?
Are you somehow under the mistaken impression that OOP does this? What happens in C++ when you have exhausted the heap and you try to new() an object? Have you ever done pointer arithmetic in Java?
That's why you get these unproductive discussions about which is best. It's like having some red-green-colorblind people and some blue-yellow-colorblind people try to agree on wallpaper for you.
I agree, it's exactly like that.
It's like that one person you're annoyed with because they keep saying the colors don't match, even though they obviously do, but you don't know that person is tetrachromatic - you don't even know tetrachromacy is a thing. Or, "picture this in your mind" meaning something completely different to people with aphantasia (like myself), and most people with and without it are not even aware aphantasia is a thing, and just assume everyone imagines (or doesn't) the world the way they do. Same thing with internal monologue - some people talk to themselves in their heads all the time (I'm in this group), others don't, and - again - most aren't aware there are people who aren't like them.
The more we talk and learn about each other, the more it seems our internal experiences are pretty diverse.