Programmers agree functions that return values are better than having side effects. What's a clear, concise summary as to why side effects are bad? Most arguments I've seen depend on "I'll know it when I see it" or "because composition", but I don't find them compelling
It's a good Q. For me, side effects increase complexity. They add edges to the graph of "what does this code do". But I also think "bad" is not the right framing.... 1/2
-
-
Side effects are things to be managed. Like complexity. Things can be built in different ways to manage complexity but it is not inherently "bad". Some systems have fundamental complexity that can't be changed. Some code requires side effects to be useful.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This was a pretty compelling alternate viewpoint (came out just yesterday)https://youtu.be/m1jOWu7woKM
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.