In a way, it seems to have similar problems to those of unstructured programming (i.e. rampant use of goto instead of procedures and loops), just to a lesser de

In a way, it seems to have similar problems to those of unstructured programming (i.e. rampant use of goto instead of procedures and loops), just to a lesser degree (since jumps that always return are still easier to understand than ones that don't). It's hard to understand the code when the control flow jumps everywhere, even when all the jumps are subroutine or method calls. A method having a good name doesn't necessarily mean it provides a better abstraction than writing the code inline, just like having well-named labels doesn't necessarily make the code easier to understand.