On Fri, Nov 15, 2013 at 1:37 PM, Gaetan <gae...@xeberon.net> wrote: > 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
All of the code samples in the tutorial could be executable/editable in the browser just like the functionality `rusti` provides in the IRC channel. _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
