> Don't be a "functional programmer", just take the ideas that are useful. But it's not about taking. It's about giving. What interfaces do you provide to so

> Don't be a "functional programmer", just take the ideas that are useful. But it's not about taking. It's about giving. What interfaces do you provide to someone else? Are the datatypes that you define mutable? Do the functions that you expose behave statefully? Do they modify the outside world? All of these things are things that functional programming (I guess I'm thinking of Haskell-alikes specifically) nudge you away from. Functional languages take power away from you to give power to someone else: the consumers of what you write (who may be youself in the future).