> Most of the troubles with functional programming come when you actually have to do something. Nah, when you say "do something", you are referring to somethin

> Most of the troubles with functional programming come when you actually have to do something. Nah, when you say "do something", you are referring to something we call "side effects" and is generally frowned upon. Your program should consist of pure functions only, be side-effects free, and there should be no state. Of course, such a program can't do anything useful, but you see, that is not the point. And if you don't see the point, you can't be helped. Am I doing this right?