3 ms·
I agree, but there's one more twist: Problems are different. Languages are chosen for ease of writing specific programs, not for "general programming". I thi
by AnimalMuppet 7y ago
I agree, but there's one more twist: Problems are different. Languages are chosen for ease of writing specific programs, not for "general programming".
I think, then, that FP is great for certain kinds of problems, and not so good for others. If you've got an FP problem, reach for an FP language. If you don't, don't.
What's an FP problem? Someone here (I wish I remembered who, I'd give credit where due) said "if you can think of your program as a pipe", then FP is appropriate. If the nature of your problem has a lot of state, FP probably isn't the answer. (Note well: problems themselves can have a lot of state. It isn't always just the implementation - the problem itself may demand it.)