Anyway, there have been updated versions of the books and content online if people are interested.
Most changes have been in libraries and interpreter / VM implementation.
Updating your knowledge from Ruby 1.8 (mid 2000s) to 3.x (current) takes little effort.
But yes, sparse API documents were always a problem because a big chunk of the community was Japanese.
https://web.archive.org/web/20230608024407/https://www.ruby-...
Btw I am contributing myself this year to the book ecosystem by writing Kamal Manual and Test Driving Rails.
I am sure more pure Ruby books will happen too by someone.
The thing discouraged me to go further was that many sections has work in progress label. I thought I might be looking at the beta docs, but no. I checked the same page down to multiple major version and the work in progress was label was still there.
Coming from Django/Laravel world, incomplete docs discouraged me to try rails.
We should see a huge reduction by the time the project wraps, but because Rails itself is constantly evolving, so to is the documentation, so you will continue to see them from time to time. Consider it a sign of growth, not stagnation.