I think a important context here is that this is engine code (a.k.a. library code).
This isn't a web service or web site where what you ship is hitting end users. The end users of this code produce new products, and the potential issues are a) that the users of the engine (i.e. game studios, internal users of Stingray etc) are being held up in their work, or b) that bugs sneak through to their users (the gamers/end users).
In this context, the idea of a quicker turnaround in exchange for some bugs leaking through is much easier to defend. The studio might want the buggy code faster rather than the fixed code later. This is probably not the case for a system deployed directly to end users.
> Why not just encourage faster reviews and smaller diffs..
That was the motivation of switching to trunk based (i.e. removinbg the incentive and slowness of larger PR's). You can't "encourage" smaller diffs other than having the process inherently do that. It's not "encouraging" to send an email to the team telling them to make smaller diffs.
If you read the article, they suggest strongly that it is hard to get a "correct" code review process (perhaps because it encourages the nitpickers, or perhaps for other reasons).
If you've got a bunch of experienced people spending a year on it that can't solve it, perhaps they just can't solve it.
And at that point: What's the difference between something that's wrong, and something that they can't do right?
Good code review is hard. Catching non petty problems is much harder then lengthy obsessing over function names or 'if' vs '?' or whether slightly more or slightly less abstraction or whether two 6 line long function vs one 12 lines long.
> Code review happens through a small window. When reviewing a PR you only look at the fraction of the code that just changed.
Their complaint is that code review makes it easy to miss deviations from global goals & style, not that they nitpick minor presentation issues.
Although I wonder what sftware they are using that would only show them a small fraction of a change…
I.e. all of the code that changed, which is a fraction of the total codebase.