r/rust•
mkhcodes

A piece of advice to the Rust community, from a novice Rustacean

First, I want to express my thanks for the people who take the time out of their day to answer what seems like the same questions over and over again. I have been very much enjoying Rust, and been thankful for the countless answers provided to the many questions spread over Reddit, Stack Overflow, and in other forums from people taking time out of their day to help a stranger.

However, it took me awhile to actually become proficient in Rust. I mean over a year. And by "proficient", I mean "able to get more than a "Hello, World" to compile. I would pick up the language, bang my head again it, and give up for a few months. And there was always some permutation of the same line that probably did more harm than good when I was ready to give up. It goes something like, "You must not have read the Rust book", or "You should really read the book before you try programming in Rust", or "the book already answers this kind of question." Even if this was done in part of a response which included additional context and an answer, I still would like to convince you to avoid this kind of language.

I'm not saying that the book itself is a bad document. It's really good! I have read it entirely through at least twice now, and have over the years read multiple versions of some chapters (e.g., the chapter on "borrowing") multiple times more. It's good that we impress upon people the significance of this learning resource. However, "You should read the Rust book" comes off as accusatory, and to those who HAVE read the Rust book (and some sections multiple times), patronizing. It's hard not to read "Anyone who is smart will know the answer simply by reading the book, and if you have read the book, then you must be an idiot."

In conclusion, I recommend that you DO continue to reference the Rust book in answers to questions. It is a useful guide. Just please try to leave the snark out of it.

​

**Edit:**

​

Thanks everyone for the interesting perspectives. Of course, I realize there are some people who are just snarky. It's who they are, and they don't want to change. I would be silly to think I can change them. I guess my post was more aimed at those who are genuinely trying to help others and do so in a civil way.

One thing I heard a lot is that it can be frustrating to deal with people asking questions who it seems haven't done enough work to ask a good question. I can understand that this is frustrating; doing what you believe is best for the person (by pushing them to do a bit more on their own) is not necessarily wrong. I guess my point is that phrasing matters. And it can be pretty simple. Rather than...

"This was all answered in the Rust book, chapter X"

...one could write...

"If you haven't already, I recommend going over chapter X in the Rust book."

It's not that much longer, and doesn't make the accusation that you didn't read the Rust book and therefore are at fault for your misunderstanding. Hopefully this isn't too much of an ask :)

Posted Sep 14, 2019, 2:30 PM UTC · edited

14063
Lokathor•

A lot of the time people come to Rust from another language, Java/C/whatever, and they initially often see that Rust looks kinda similar visually so they assume it's similar linguistically.

So they dive right in trying to use idioms from their last language in Rust, getting frustrated, and then when they ask for help people explain what's wrong in terms that are basic if you read the book, but which aren't at all familiar if you haven't read it yet. I seriously know a guy who spent six months trying to make a circuit simulation program, including extensive macro usage, without reading the book past chapter 5. It's wild.

While I agree that "read the book" is absolutely not the end of learning Rust, it's certainly fair to always check that a person asking a question has read the book before proceeding with a Q/A session.

98
anlumo•

Yeah, I'm currently doing interviews for a programming job where part of the description is programming in Rust. I've had multiple applicants who said “yeah I've looked at some Rust code in preparation for this interview, and it didn't look hard at all”. Yeah, right…

52
hniksic•

I've had multiple applicants who said “yeah I've looked at some Rust code in preparation for this interview, and it didn't look hard at all”. Yeah, right…

My experience doing interviews is that a lot of people tend to claim to be acquainted with Rust just to appear up to date with modern programming. Many of them have read through the book or a tutorial, but have never written a line other than hello world.

A simple question to differentiate between those and the ones who have actually made an effort to use Rust is something along the lines of "what are your experiences with the borrow checker?" If the applicant responds with something like "it's ok" or "I haven't gotten that far", you can rest assured that they haven't done any Rust programming. (Unless the applicant is a genius, that is.)

Responses from folks who have used Rust in practice include "fighting with it all the time", "used to fight with it, but it's getting better", "hate it with a passion, but it saves my butt", "annoys the hell out of me", and so on.

23
PyroLagus•

Responses from folks who have used Rust in practice include "fighting with it all the time", "used to fight with it, but it's getting better", "hate it with a passion, but it saves my butt", "annoys the hell out of me", and so on.

I kinda like it when compilers yell at me. Whether it's the Rust borrowchecker or the GHC typechecker. Am I weird?

21
CrazyKilla15•

Seconding this, I don't think of it as "fighting" the borrowchecker, i'm "working" with it. It stops mistakes and bugs for me, it isn't trying to stop me from writing code or anything. Mindset matters.

11
tomwhoiscontrary•

Short-lived early noughties gonzo techno act The Laziest Men On Mars, best known for their track Invasion of the Gabber Robots, which was the soundtrack to OG internet meme All Your Base once wrote in an interview, now lost to the web:

What's the secret to our success? Shouting Robots! People love it when robots yell at them!

So, well, yes, you probably are. But you're in good company.

2
Omniviral•

I'd say that my feelings to borrow ckecker is about the same as to type ckecker. It has its annoying limitations, but today you rarely hit them thanks to nll.

Do I sound like experienced Rust dev? :)

13
anlumo•

Heh, if you hate it you're doing it right. If I ever encounter somebody who actually claims to know Rust, I'll sure ask that question!

btw, I just posted our job ad here.

3
RecallSingularity•

Whenever I feel sad about the borrow checker, I just remember that soon I will be able to use a lot of threads and my code will "just work."

But issues around references to temporary objects can be a real pain..

1
elniallo11•

I have a definite love/hate relationship with the borrow checker. We’ve managed to work out most of our differences lately though

3
Wolvereness•

My response would probably be "I've learned to appreciate it - the reason I like Rust is because the language enforces borrow checking".

3
hniksic•

And that's a perfectly convincing response, the key being learned to. Someone who never noticed the borrow checker or who never had issues with it has probably not really used Rust. It would be the Rust equivalent of a C or C++ programmer who has never experienced a crash.

2
kwhali•

Responses from folks who have used Rust in practice

I remember getting one of my first Rust programs working nicely but all as one big long function. Then I was like right, time to tidy this up into smaller functions and structs before I continue with this any further. I thought that since it works fine as is, this wasn't going to be a difficult refactor, like any other language that I've done such.

Hello borrow checker, 99 errors at compile, 99 errors at compile, you fix them all, then compile, 99 errors at compile. Legit experience, so many borrow issues cropped up once I broke all that logic out, I'd fix them, and to my surprise it only revealed that there were more issues somehow.

At one point... it's "WTF just bloody compile and let me run the damn code, enough of your whining damn it!", while at the same time it's also "Wow, I'm really bad at avoiding bugs, I love you borrow checker (and other assorted compile time errors)", especially with those niche cases that get picked up during compile that you'd only otherwise be aware of during run-time and only if you noticed something was actually off.

So it can be a hassle and slow me down, but I like the additional confidence when it compiles happily, I feel that I don't need to offload a bunch of checks in a test suite for ensuring a similar amount of trust(not that tests aren't still useful, if anything the overall value of what remains is higher).


Did I pass the question? 😎

TL;DR: My reaction to the question. While also being like this afterwards.

2
wishthane•

I find that it really encourages you to modularize your code in the first place in order to avoid the hassle of breaking things apart later, which takes a lot more organization in Rust than in other languages.

This has been a very good thing from my experience.

1
mkhcodesOP•

I've heard from you and others the problem of wanting to answer questions, but finding so many people who appear simply haven't done the work to propose a decent question. I can sympathize with that, and perhaps I didn't do a good job explaining my issue.

By all means, I think it's commendable to try to get those who ask sub-par questions into a better situation by asking them what they've done first. However, I think phrasing is important. My post is really just an ask for rather than saying something like "You should have read chapter X of the book", one phrases it as "If you haven't already, read chapter X of the book." From someone who has read the book, the change in phrasing brings the comment from snarky to benign.

I apologize if I didn't do a good job making this clear in my post.

4
Lokathor•

Oh no no, we all have out own brand of English, and it's very easy for written mediums to mangle tone and intent. I doubt that people are trying to be snarky very often, but it can easily still seem that way.

2
mkhcodesOP•

I agree. Hence this post, where I'm hoping I can improve things, if only a small amount.

1
bstaletic•

Just to be clear, I've not gone much further from "hello world" in rust.

That said, I tend to disagree with "don't tell people to RTFM". More specifically, I don't see any difference between "You should have read chapter X of the book" and "If you haven't already, read chapter X of the book".

 

Actually, the more I think about it the more I'm convinced that I'd prefer to be given the first answer. Because it tells me that I have definitely missed something and should read that thing again. The other reply sounds too "wooly" and I might brush it off as "I read it, I can just skim over it again to refresh my memory". There's also the fact that some questions are repeated over and over again and for those RTFM is very much suitable as rehashing the answer is a waste of time.

TL;DR: Even when asking a question, I prefer the more aggressive RTFM.

2
mkhcodesOP•

That said, I tend to disagree with "don't tell people to RTFM". More specifically, I don't see any difference between "You should have read chapter X of the book" and "If you haven't already, read chapter X of the book".

I can see that. Unfortunately, I guess different things work for different people.

Actually, the more I think about it the more I'm convinced that I'd prefer to be given the first answer. Because it tells me that I have definitely missed something and should read that thing again.

The other reply sounds too "wooly" and I might brush it off as "I read it, I can just skim over it again to refresh my memory".

I guess this is my issue. I don't really see where it's useful to think that once someone gets stuck with something in Rust, it should be required to reread an entire chapter or two of a book again. In my experience, I learned the most when I ran into problems not from the book (which laid the groundwork for my learning, certainly), but from the people who have provided more in depth answers, taking real-world examples that look much different from those in the book and explaining them in their own way. Eventually, one of these explanations would click.

There's also the fact that some questions are repeated over and over again and for those RTFM is very much suitable as rehashing the answer is a waste of time.

Unfortunately, I think there is going to be some implicit friction between trying to maintain a novice-friendly environment and trying to increase the efficiency in responding to the most basic of questions. My post was not directed towards the community at large in an attempt to make it more efficient, but rather at those who are trying to make things more welcoming to novices. I understand the point about trying to not allow forums like this to become only a den of very basic questions, and I don't pretend to offer any solutions to that problem.

Thank you for remaining civil in this discussion.

1
bstaletic•

Unfortunately, I guess different things work for different people.

Exactly what the most of my previous post tried to say.

I don't really see where it's useful to think that once someone gets stuck with something in Rust, it should be required to reread an entire chapter or two of a book again

I'm just talking from my experience. In communities that have great documentation (Arch, Gentoo, FreeBSD, OpenBSD - to varying degrees), I did ask questions and got RTFM style responses and not for a single moment did I think that the person responding should have given me a chewed up answer. Instead I (re)read the chapter of the handbook or the wiki page and, if needed, asked a much more specific question regarding a thing I read that I either didn't understand or didn't provide the expected results.

I learned the most when I ran into problems not from the book (which laid the groundwork for my learning, certainly), but from the people who have provided more in depth answers, taking real-world examples that look much different from those in the book and explaining them in their own way. Eventually, one of these explanations would click.

I absolutely agree, but this means that a few things happened before you had to as the question:

  • You read "the book".
  • You tried to apply what the book said and failed. Or it wasn't clear how to apply something from the book to the problem you were solving.
  • Presumably, you were either explicit about what you have tried to solve your problem.

If all of the above is true, I absolutely agree that "RTFM" has no place.

Unfortunately, I think there is going to be some implicit friction between trying to maintain a novice-friendly environment and trying to increase the efficiency in responding to the most basic of questions. My post was not directed towards the community at large in an attempt to make it more efficient, but rather at those who are trying to make things more welcoming to novices. I understand the point about trying to not allow forums like this to become only a den of very basic questions, and I don't pretend to offer any solutions to that problem.

I agree with you here as well. Note that I make a distinction between "a basic question with 0 research" and "a basic question that shows some effort". The first kind is of questions are by help vampires and I absolutely don't see anything wrong in telling them to RTFM. The other kind shows willingness to learn and should be helped out.

Today's example case 1: A user cloned my software and started it. It's written in python except a core piece which is in C++. On start the error was "Core not compiled. Check the README for instructions." That guy came to me and said that he's getting a "weird" error that says <quoted error here>.

  • Me: Have you compiled the core?
  • Him: Yes.
  • Me (still in doubt): Is the file foo.so in folder bar?
  • Him: No.

Are you telling me that sending him a link and saying "read the instructions" was too harsh?

What I'm trying to say is "RTFM" has its place in two cases:

  • The one asking the question clearly didn't try anything and is being a help vampire. The asker clearly doesn't understand the difference between a paid tech support and a free community of volunteers.
  • The one asking the question clearly missed something really big, maybe because he didn't get that far in documentation. No need to be rude, but by all means, point the asker in the right direction.

 

Lastly

Thank you for remaining civil in this discussion.

Absolutely no need to thank me. We're exchanging points of view that obviously differ in some aspects, but there's no reason for anything but civil discussion.

5
crabbiepatties1•

Hey dude did he ever finish that program and if so could you tell me more about it? PMs open

2
Xychologist•

While I can appreciate it might be frustrating, anywhere novices ask questions need to have a very clear chain of requirements - RTFM, UTFSE and think hard about what you found before asking a question. Especially with beginner questions (in any area, not just Rust) most of them have been answered before many dozens of times and have absolutely no reason to be discussed again.

If the Book is inaccurate or incomplete, AND there's no existing Reddit thread or StackOverflow question, then it's good to raise. On the other hand, if someone's just coming over from $language and hasn't spent the needed few days reading in detail yet, they need pointing back to the beginning of the process.

This doesn't just apply to Rust. Reddit in general is very, very nice to people who haven't done their research relative to many other places.

25
fintelia•

Another common requirement is to indicate what you've tried so far to solve your problem. Saying "I've tried reading the parts XYZ of the book, but I didn't understand..." is a perfectly valid/expected component of that

23
general_dubious•

Yes. Indeed, asking for explanations about the book is very different than asking a question whose answer is in the book. The thing is, there is always the case that someone who doesn't understand the book either doesn't know they didn't understand it, or doesn't realize the answer is there. The point I'm raising is that you can't actually expect every single beginner who actually put in the effort to ask questions the right way. Our job here is to answer in a way that leaves the redemption door open. So instead of saying "read the book", one could say "the answer is there, have you read that? If no, read it; if yes is there something you don't understand?".

8
ergzay•

If the Book is inaccurate or incomplete, AND there's no existing Reddit thread or StackOverflow question, then it's good to raise.

There's a difference between inaccurate/incomplete and "not explained well enough". It may have a full explanation but the language may not be something the reader can grok.

4
Xychologist•

While true, in this particular case I would actually roll that into "incomplete". While most technical books have no need to be clear to those with no background, things like the Rust Book are explicitly aimed at new Rust devs, so if the information is there but opaque to a new Rustacean that's a bug with the Book rather than with the reader.

Contrast to the Rustonomicon, which new starters don't really have any business reading and can thus rightly assume a good grounding in Rust in general on the part of its readers.

6
ergzay•

Then your book is infinitely long. Everyone has different skill sets. There is no perfectly explained book.

2
mkhcodesOP•

I am hearing a lot of this sentiment, that it is frustrating for people who are spending their time answering questions to be answering either the same questions, or to be answering questions from people who could have put more time in to solve it themselves. No doubt, this is something that all online communities deal with (I remember StackOverflow posting a thread specifically about "civility", probably around this same problem).

I guess I don't have a good response to this. I can understand this frustration. Hopefully this thread stirs up some conversation on how others deal with it in a way that is amenable to both sides.

2
IshKebab•

I 100% agree. Also I think there is an aspect of the Book that is a bit misleading (at least when I read it). It presents the "happy path", especially with things like the borrow checker. Before NLL you could easily read the book, think "this borrow checker doesn't sound so bad" and then have a go yourself and immediately be hit by a brick wall when it isn't smart enough to understand your code.

You've read the book, you think you understand the logic behind checking borrows, but the book barely mentions how dumb the borrow checker is and that you will probably have to contort perfectly safe code into a form that it understands.

Maybe that's been fixed by now (well it partly has by NLL) but when I read it I remember feeling pretty annoyed that everyone was like "borrow checker saves you! So awesome! You just need to understand it - no downsides!". Very few people said "Oh btw loads of programs and even little snippets of code that are perfectly valid and would be fine in C++ don't work because the borrow checker isn't smart enough to validate them."

/rant

22
cvvtrv•

I think in some ways the old version of the book were better at this. They went through a lot of the borrow checking more explicitly. There was less a focus on the happy path and a bit more willingness to go into detail early on. That expects more of your readers, but I know for me it was useful. As someone writing Rust for a while, I feel parts of the newer book aren't useful to me now because they gloss over things. I think some of this is a result of the borrowchck being much smarter and not corresponding as closely to scopes. It's harder to explain now. I don't really blame the authors though, it's a hard balance to strike I'm sure.

10
binkarus•

I find the book tries to be too conversational at times, which makes it difficult to use as a strict reference even after having read it. I wish there was a version which was a strict technical guide aimed as a being reference, like having a grammar definition, control structure list, lifetime syntax guide, definition of where impls can be defined, where structs can be defined (e.g. I don't even think it's mentioned in the book that you can defined fn level structs), etc. The literal rules of Rust, and not an tutorial. I'm an advanced programmer, so I don't really need to learn how to borrow again, I just need a list of the rules I need to follow because I program in at least a dozen different languages and sometimes take a break from writing Rust.

It's also changed significantly since the first time I read it.

So, overall, I do think that there are problems with the book.

15
Nextil•

Like the reference? It's one of the many books included with the distribution (rustup docs).

18
binkarus•

Yeah pretty much. That is about 75% of what I want.

5
emefluence•

As someone coming from a dynamic language background it was pretty clear to me from the start that Rust is the kind of language where you HAVE TO read the whole book first and, as you have found, you're going to need to re-read some bit of it over again. If people with problems don't mention that they have read the book I think it's fair to ask if they have and, if they haven't, suggest they do.

I love languages where you can just dive in and start hacking like python and javascript but Rust is clearly very different, even from other compiled or strictly typed languages. In my experience if you phrase your question such that it is clear you have read the book but still don't get some part of it then fewer people will be snarky to you.

Also, it's easy to perceive snark and hostility that isn't really there online. Programmers can be brusque and terse, it doesn't always mean they think you're a lazy idiot.

10
mkhcodesOP•

Thanks for your response.

Yes, one thing I didn't point out very well is that there are, indeed, people who will not seem to put forward the minimal effort to solve things on their own, or even to reduce their problem set to some minimal amount of code to make it clear to others exactly what their question is. It's frustrating to want to help people, but feel like the community is just these types of people. I won't pretend I know the answer to this dilemma.

That being said...

Also, it's easy to perceive snark and hostility that isn't really there online. Programmers can be brusque and terse, it doesn't always mean they think you're a lazy idiot.

I agree with this in theory, but I worry people online (and programmers specifically) use this argument as a crutch. Rather than try to improve how we communicate online, we just say tell people to not read between the lines. So my question is, what is more helpful to the community: that we try to train people (who are often new) to not be worried by the norms of the community, even if it seems hostile at times? Or do we try to get people (who often converse with new people) to be careful how they speak online to appear less hostile?

I realize I can't change everyone's mind. Hence why I specified this as advice, rather than a directive. But I hope there are those who are empathetic and are genuinely interested in helping others, that a simple change of wording can go a long way.

6
Eh2406•

I won't pretend I know the answer to this dilemma.

I think the dilemma runs deep. Humans remember bad experiences more than good ones, and are really bad at estimating the occurrence rate of rare events. The responders remember the "lazy idiot" that did not try to inform themselves, even if it is only one in a hundred askers. The asker remembers the "snarky response" that they saw, even if it is only one in a hundred responses. I suspect the real rate is higher than that for both, but the point still holds even if it was that rare.

So my question is, what is more helpful to the community: that we try to train people (who are often new) to not be worried by the norms of the community, even if it seems hostile at times? Or do we try to get people (who often converse with new people) to be careful how they speak online to appear less hostile?

Being a dilemma, the ancere has to be both. Hopefully we can teach members of the community (both new and old) that one of the norms of this community is assuming good intent from the other members of the conversation. Hopefully this thread will help all to be more careful.

Speaking of witch, let me go find that comment I made earlier today and edit it to be more clearly respectful.

3
mkhcodesOP•

I think you've summarized the problem quite well. Thank you for taking the time to consider this.

2
_boardwalk•

I think my issue is with people who:

  • Haven't really thought about their problem and either don't describe it well enough and/or have a clear XY problem, or
  • Are treating r/rust like a place to learn how to program and are asking questions that aren't Rust questions at their core

The problem with this medium (social media, for technical subjects in particular I suppose) is that it amplifies both ways: You can either get a variety of interesting input from asking an interesting question, or you can waste a whole lot of people's time who now have to scroll past a waste of a post.

For me, at least, I turn reddit into emails, so I see and deal with posts once, rather than seeing them linger for hours/days. That makes it a little better.

In the end there's probably no point in saying this, because the people who are the type to do it will continue to do it. And my list of subscribed subreddits (in general) will continue to shrink. (The Rust-the-game posts are more annoying anywho ;)

9
PsylentKnight•

Are treating r/rust like a place to learn how to program and are asking questions that aren't Rust questions at their core

If they're learning Rust as their first language, then where besides a Rust community would you expect them to go? Most general programming subreddits are geared towards more mainstream languages like Java and Javascript.

7
_boardwalk•

That's a good question. If this was a few full-fledged forum, we could have a subforum for it. Even the official Rust forums only has a very generic "help" tag.

1
mkhcodesOP•

You and others have pointed out the frustration of dealing with people who probably haven't put forward the minimum amount of effort that is informally required on these sites. I can understand the frustration with dealing with that. I don't really have a solution to that problem (it goes well beyond this one forum, or even Rust in general; heck StackOverflow had a huge kerfuffle about this exact problem of "civility").

I guess my hope was that people who are honestly trying to be helpful by saying something like "You should read the book" could realize how snarky this comes off. My advice is simply changing a line like that to "If you haven't already, consider reviewing Chapter X of the Rust Book" just works so much better.

2
calligraphic-io•

How do you turn reddit into emails? That sounds like a good idea for slow-moving subs where I'm deeper and want to see everything posted. Python script?

2
_boardwalk•

Yeah, a Python script as a cron job. There are packages out there like rss2email that you can plug reddit's RSS feeds into, but the problem is that, unless you're sorting by "new," the posts reorder themselves and it confuses rss2email. At least the last time I tried it a few years ago.

Unfortunately I would have to clean it up to put it up somewhere, and I am very, very lazy.

1
dooblevay•

Not everyone can learn by reading a book. I don’t recommend replacing it with asking questions on Reddit but some of us learn better by doing or watching. I’ve had a lot more success reading other people’s code and watching videos, but don’t have a go to channel or anything. It would be amazing to find a channel that had someone explaining things in detail.

Otherwise I just type code and let the compiler teach me. It’s really something else.

9
GideonMe•

Thank you for saying something OP. The fact that you are bringing this up indicates that we have a problem that is not being addressed.

It's extremely discouraging when you're beating your head against a wall trying to grasp a new concept, and someone responds to your request for help with what is effectively "RTFM".

People learn in different ways, and expecting that any one method of learning (and to be specific to this post: any one book) will explain the concept to absolutely everyone is unreasonable.

Also, reading is hard. I really struggle with concentration while reading technical documentation. I often have to literally highlight my way through a book to stay focused. This is ok, and I'm definitely not the only one who faces this problem -- and many people have more severe concentration challenges than I do. As a community I hope we are not in the business of shaming people for feeling intimidated by a five-hundred-and-sixty page technical document.

It should never not be ok to ask for help. If someone is asking a question that you don't personally find intriguing, you are not required to answer it. Even if a person asks for someone to walk through their code with them line-by-line, this is ok. (Of course you are always welcome to decline. In fact please do so if you have reached your limit.) But do not shame people for needing extra or different kinds of help. And know that there are cases where the act of referring a struggling newbie to The Book can have negative side effects.

​

To my fellow commenters in this thread, I'm frustrated and disappointed by the lack of empathy in many of your responses.

  • Yes, question-askers ought to respect one another's time.
  • Yes, many people find that Rust has a high learning curve, and is Not Like Other Languages.
  • But this does not excuse having a "RTFM" attitude.
  • It is unfair to be suspicious of everyone who asks a question because sometimes people are less informed than they believe.
9
mkhcodesOP•

Thank you for your response. To be sure, I don't think this is a LARGE problem, but I have to agree that some of the responses to this post (including the PMs I received) have been less than empathetic. I guess I might have stirred the bees nest, which given human nature, might be unavoidable from some members.

Hopefully, however, the people who upvoted the post were able to take my message as all it was meant to be; a piece of advice, not some sort of indictment.

2
the_gnarts•

Tbf most people I personally know who got into Rust or are about to do so, would recommend “Programming Rust” instead. I usually let them borrow both so they can choose the one that suits them most, and so far (n = 3) the consensus seems to be strongly in favor of this book.

However both books have one issue in common: while they explain core language concepts, they are of little use when you start exploring the larger ecosystem. The learning curve does not become less steep once you are familiar with what’s covered in the books. Since much of Rust’s utility today (as opposed to five years ago when I got into the language) rests on concepts like futures and async which are quite recent as far as the language evolution timeline is concerned, there is little canonical introductory material available, and much of it like futures 0.1 will become largely obsolete soon.

Of course from my perspective things are not even remotely as volatile as in the pre 1.0 days but that is little consolation to someone starting out in the present.

8
adante111•

Just to offer another beginner perspective (who has only just finished the exercism rust main track): my experience with the rust community* (mainly via r/rust and discord) has been incredibly positive, and to be honest at no point have I been told to RTFM, despite several times when it should have been reasonable (I did read the book, but took a hiatus, and forgot a lot). My reddit comment history is peppered with the most banal questions pretty much all of which have been patiently answered with some really informative multi-paragraph responses. My experience on the discord has been similarly positive.

(*My experience with the language itself feels like a mental hazing, but that's an entirely different matter and not meant to cast any aspersions on rust.)

3
photochemsyn•

Some people don’t seem to understand that among the best ways to solidify and expand your own knowledge is to answer questions posed by people with less knowledge, and that’s why teaching somebody something is the best way of learning more about the subject. Anyone who responds to a question with ‘read the book’ is just wasting their own time and everyone elses and cluttering up comment threads. On the other hand, if people do answer a question and provide valuable information, but toss in some snark on the side, well, that’s OK. If that bothers you well, I recommend growing a thicker skin, as the online world is not known for its civility and polite mannerisms, for whatever reason.

Here is a nice example of how to (the main answer) and how not to (the comment) answer a rather basic beginner’s question on Rust: https://stackoverflow.com/questions/57848114/what-are-the-differences-between-and-vec-declaration/57848340#57848340

Personally, I tried to dive into Rust and quickly realized it was an advanced language, by which I mean it was created to solve some fairly advanced problems like concurrency issues such as data races, and memory issues of the leaky variety, and it had quite a few functional programming concepts wrapped into it. So my approach to learning Rust has been to dive into C and get a better grasp of the kinds of problems Rust was created to solve, and also take a little dive into some functional concepts (easier in Python, harder in Haskell) to understand how that part of Rust works. After some more of that, I’ll be ready for another go at it.

2
[deleted]•

[deleted]

1
belovedeagle•

TL;DR: Asking people to read the book is unacceptable!!1! Oh wait, I never considered how frustrating it is to get an endless stream of low-effort questions drowning out the people who have legitimate questions needing help. Okay, you can ask people to read the book after all, but only if you use u/mkhcodes -approved language. Also, snark and sincerity are mutually exclusive because it's not my preferred communication style.

LMK if I read this wrong.

1
[deleted]•

[removed]

1
stewartm0205•

Rust has a high learning curve, higher than most languages and it is still in flux.

-1
wtfbbq7•

Read the book first then go rust sounds accurate. I'm reading now and have glossed over countless repos in git too.

Asking people to repharse it so it will a less ego bruising just sounds whiny and immature.

-4
mkhcodesOP•

Read the book first then go rust sounds accurate. I'm reading now and have glossed over countless repos in git too.

Nowhere did I say that we should stop referring people to the book. In fact, I tried to make explicit that we should point them to the book.

​

Asking people to repharse it so it will a less ego bruising just sounds whiny and immature.

I'm sorry you feel this way, but I disagree. There's probably no use in continuing the discussion in this manner.

1
wtfbbq7•

No where did I say that you said "that we should stop referring people to the book".

RTFM is a thing for a reason and it appears it hurt feelings if not suggested exactly as you'd like. Sorry.

-1
[deleted]•

[deleted]

-7
anlumo•

Of course they're free to do so, but OP is also free to have a bad opinion about them. This is not about not allowing snark, this is about not recommending to do so if you want to be inviting to newcomers (especially considering that being open to newcomers should be a major goal for a new community like Rust).

15
[deleted]•

[deleted]

0†
anlumo•

You said that you should allow people to be snarky when it's in their nature. My argument is that that's not a good idea if you want to be an open community.

Those people can be snarky among equals, that's fine, but not towards newcomers.

10
spin81•

That’s... not what I said.

If it were, it would not be a response worth making, would it?

1
mkhcodesOP•

They are free to do so. As I wrote, this is just advice, not an ultimatum. My hope is that people do care about how their words affect people, and don't realize the impact of what they are saying. For those people, I hope I can be of use.

For people who are intentionally being snarky, I realize there's not much I can do there.

6
[deleted]•

[removed]

-8