How to Control Haskell Side Effects

In most languages that don't do this, it is the norm to just ignore the things that can go wrong. Haskell has this mechanism for baking side effects into the type system in a way that if your code uses networking, that's baked into the type signature. So you cannot avoid accepting, noticing, dealing with the fact that you are now subject to the side effect of networking. It does that primarily through the word I was going to try and avoid saying, but you can't discuss Haskell for an hour without saying it through monads. Yeah. But I think people often confuse up monad are Haskell is trying to get rid of side effects and then it realized early in its inception that