I agree on the semantic point. The job of technical writer is quite a talent to have, not anyone can easily vulgarize concept and present them in a logical way. This is pedagogy and quite hard to set up in a developer's brain.
However, on tutorial I think there is a flaw: most of the a time, just the source code itsn't enough. If you want to test and play with it, you need some other files (makefiles, crates declarations, ...) to have it running. While it's good to have the code sample right on the screen, if I want to take it and paste it to test its behavior, i have to deploy a large among of work, to find similar compile samples and replace the files. I would recommend to have some kind of "package" with makefile and source code easily accessible, described early in the tutorial. Not completly described, but it basically say: "don't try (yet) to understand what all these Makefile and lib.rs and other stuff do, just edit the "sample.rs file and type "make". I would love to have this package automatized and freely available on each source code trace in the tutorial. ----- Gaetan 2013/11/15 Daniel Glazman <[email protected]> > On 15/11/13 15:59, Daniel Micay wrote: > > > It's gets across most of the information, but it doesn't have a very > > compelling flow of examples. It teaches how to use language features > > rather than walking through building something with those features. > > > > For example, the sections on owned boxes and borrowed pointers could > > be done by walking through the implementation of a singly-linked list. > > It's incredibly hard to actually do this without using too many > > features before they've been introduced. > > Exactly my point. > > Marijn (hey Marijn!!!), nobody "hates" your tutorial. It's an excellent > document, but made for programming language specialists with an already > quite advanced level. My comment was an optimization comment only: > tweaking a bit the way examples are chosen and designed, and explaining > better some complex vocabularies, it will attract more people to Rust > and will help smoothing the learning curve. That's all. > > </Daniel> > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
