[notes] On the Rust Book Maintenance

It is indeed not optimal. Unfortunately, it is also hard to solve. Assumed audience: People at least broadly familiar with the Rust ecosystem and The Rust Programming Language Book’s role therein. Thinking a lot about the comments in The many journeys of learning Rust about the perceived maintenance state of The Book: “We’d like to use [The Rust Programming Language/‘the book’], but we’ve found that it’s out of date, unfortunately. We’ve looked at the GitHub repo and found it’s got a lot of unresolved issues and unmerged PRs” — Principal Software Engineering work on Rust adoption in a regulated industry There’s something to this: there are current 261 unresolved issues (many of which we haven’t even commented on) and 195 open pull requests (and we also haven’t even looked at many of those). Some of those are long-standing “this needs more time and effort to figure out how to tackle” kinds of things, some of them are typos, some of them are style arguments, some of them are valuable…