The problem isn't so much with PRs themselves but the journey up to the PR. If the reviewer has no context of the work, or the author has diverged too much from what was planned, things can quickly get messy with questions and knowledge sharing that should have been done before the code was written in the first place. I don't see PRs going away any time soon but they should be treated more as a part of a CI/CD pipeline and less as an actual code check.