Why don't technical books have a issues page?
What's is assumed as correct might not be tomorrow.
Many technical books suffer from that, being it small technicalities or huge issues.
Some books have new editions to solve that, however many don't and even then it would be useful to know inaccuracies present on each edition.
A simple issues page referenced in the beginning of the book would be golden, why inst it a thing yet?
You are thinking of errata, and most technical books do have it.
I meant a issues web page like bugzilla or github.
Like this?
https://www.oreilly.com/catalog/errata.csp?isbn=9781491949467
Oh that's is so cool !!! I have read a few O'Reilly books how did I never noticed this.
Technical books have long had errata pages, but often with new issues, known errata are usually fixed. And as mighty as their may be, editors can't list errors that haven't yet been identified. To be in errata, it has to be found too late to fix, but not too late to change.
They often do?
What book(s) are you referring to?
Do you mean a kind of introduction-style insert that addresses things a revision would state?