This is what I don’t get about FP, in exchange for code that looks more elegant, you get something that is much more of a PITA to debug. If there is a problem, I often find getting rid of the indirected plumbing and directly exposing control flow to be the best way to find out what is going on when and where.

It is only a PITA to debug on paper, not when using a graphical debugger.

How so? Visual studio still doesn’t reveal the right context when you actually find out the error has occurred.

Visual Studio isn't the only option.

https://blog.oz-code.com/debugging-linq-available-tool-compa...

https://www.oz-code.com/

Nice! Tooling is a large part of my trouble with FP, better tooling would make it easier to debug, especially those complex signal networks that require different debugging paradigms from imperative languages.

This suggest that it's difficult to reason about the code. That's the last thing I want.