Why does the rust documentation still suck? It basically only works if you already know what you ate looking for, and still is difficult to read.

Compare the string pages.

Rust: https://doc.rust-lang.org/std/string/struct.String.html

Java: https://docs.oracle.com/en/java/javase/11/docs/api/java.base...

C++: https://en.cppreference.com/w/cpp/string/basic_string

Yes, the cop page probably has some bespoke work on the page, but it still demonstrates ideas that are partially auto generated (and most of that page is auto generated).

* the method and functions aren't sectioned in any useful way. Just a list of functions (solved by adding section and subsection to the doc comments). Methods that create, search, mutate, test, transform, etc should be sectioned off.

* no use of alignment, just blobs of text

* poor use of color. Both java and cpp use color to break up sections and alignment to distinguish different parts of the signature. Rust is just a page of text that is very difficult to scan.

* no summary. Cpp summarizes the group of method before clicking b through to individual listings, while java summarizes each method at the top. This is useful for searching in a page. Rust is once again just a block of text.

* rust also has a unique issue in how to organize traits and other rust specific constructs. It really should have figured this out by now.

I can keep going on the uselessness of the rust docs, and I say this as someone who was involved in the language in the past, and give it a new shot about once a year. But the docs have always sucked compared to other languages.