I have to admit that the sales pitch of the document is on point, however they could leave the revision history out as I see not much value added there.
You can bring it up as an issue on github. They can probably move it down to the bottom.
The change log has A LOT of value if you are trying to figure out what version you should upgrade to.
If you are stuck on an older version, then you need to understand what value you gain by potentially introducing new bugs into your product.
They also credit everybody who has worked on the project, which is super important.
You have a good point, thanks. Maybe my reflexion was more about the scope of the pdf, no point in bundling things not relevant to learning the library and that maybe need easier discoverability than a pdf anyway.
It is quite navigable. You can click anywhere on the table of content and it will get you right there. There is also a sidebar with bookmarks that work. You can basically skip 70 pages. Considering it is already 2000 pages, you have to use the table of contents already.
The scope of the PDF is to be the full documentation.
If you were used to doing something a certain way, you need to know that things changed.
