One of the problems with Tokio is that, after all this time, they still don't have a book.
Follow
Writing a book about your library is basically a requirement in the Rust ecosystem.
One of the problems with Tokio is that, after all this time, they still don't have a book.
Writing a book about your library is basically a requirement in the Rust ecosystem.
@juliobiason That's good. As long as the parts are cross-referenced and may be read in any order. And most importantly the interface doesn't break compatibilicy every few months, rendering all the knowledge useless.
I really prefer it when people sit down for a long period of time, think deeply about every detail, and then after release leave the specification alone for a decade or so.
If somebody wants to change the interface in the meantime, they define another specification to coexist with the former, not to supersede it.