In my personal opinion when I'm reading code and trying to follow execution flow, OOP's "Everything happens elsewhere" approach is really annoying. In a Java co

In my personal opinion when I'm reading code and trying to follow execution flow, OOP's "Everything happens elsewhere" approach is really annoying. In a Java codebase for example I would need to find all implementing classes, then search for that one method being called in each separate file. This means opening multiple files and searching for a few lines of code in each file, just to see what happens. Written in a pattern-matching style there is a nicer correspondence between code-locality and execution-locality - which matches my mental model much more nicely, rather than OOP's colocation of different behaviors on the same entity