While you're correct, part of the fix for that is not to publish a 500-page paper in isolation. You instead publish the underlying concepts piecemeal in "easy"-to-understand chunks (for this insane level of "easy", hence the quotes). This works the same as how good practice when writing code is not to drop a 50 ksloc commit, but rather to do a series of patches showing how you arrived at a given solution.