4 ms·
I'd also like to mention that getting to the documentation for anything with Rust is fairly annoying, mostly because a ton of the stuff in the book links to the
by sondr3 8y ago
I'd also like to mention that getting to the documentation for anything with Rust is fairly annoying, mostly because a ton of the stuff in the book links to the first edition and getting from the first edition to the current one is really cumbersome. It'd be great if you would be redirected from the old book to the latest version instead of getting to it and only get a warning that it isn't the latest version. Especially since there's no easy way to go from the first edition chapter to the corresponding one in the latest, it's at least three-four clicks and annoys me every single time.
- steveklabnik 8y agoCan you please file bugs when you see this? I'd be happy to update them to point in the right place. We have some constraints that make plain redirects really hard; we cannot run a web server or use a ton of JavaScript, for example. Maybe this situation is painful enough for community consensus to change...
- mwcampbell 8y ago> we cannot run a web server or use a ton of JavaScript Just curious, why are those constraints there?
- steveklabnik 8y agoThe documentation is distributed locally, as static files, as well as being available on doc.rust-lang.org. This is considered a big feature. I personally would love to tell people "sorry, you have to run a basic web server, even locally" for a few reasons, but it doesn't feel socially viable at the moment, sadly :/
- mwcampbell 8y agoHere's one way you might be able to make the case: If you require a web server even locally, then the docs can be installed as a single file (zip archive, SQLite database, etc.). This would eliminate the overhead of lots of small files on at least one popular desktop OS, speeding up installation and updates.
- steveklabnik 8y agoThis is already an active discussion, yep. We'll see...