3 ms·
Assuming you wrote this, you lost me in the book analogy. Once you wrote "let's ignore programming for a moment" I thought to myself, why am I here? And why are
by jsmthrowaway 12y ago
Assuming you wrote this, you lost me in the book analogy. Once you wrote "let's ignore programming for a moment" I thought to myself, why am I here? And why are we talking about ownership? How do I set up a tool chain and write hello world?
This doesn't strike me as a 30 minute intro to Rust. More like a quick guide to what sets Rust apart from C. Perhaps my expectations would be different with a different title ("How Rust can benefit you as a working C++ dev")
- steveklabnik 12y ago> Perhaps my expectations would be different with a different title Hmm yes, I will think about it. Ownership is Rust's most important and unique concept, so an intro to ownership _is_ an intro to Rust. I will think about how to make this more clear.
- Scramblejams 12y agoI had no problem with the book analogy. I've been hovering around the periphery of Rust for a while, waiting until I understood the ownership thing before I move into it more seriously. Thanks for writing this! I think it was a solid step in the direction of clearly explaining ownership. I know more than I did before and I'm looking forward to reading your next piece on it. Good work.
- steveklabnik 12y agoThank you! The URL to watch is http://doc.rust-lang.org/guide.html http://doc.rust-lang.org/guide.html . I'm working on it every day. Two more sections should land tonight, and I'm writing the next one as we speak... don't hesitate to ping me with ways the docs could be better, either on IRC, email, or just opening an issue on the repo and CC'ing me.