5 ms·
As a counter-anecdote, I'm in a very similar boat as the parent comment, and I have been astounded how consistently all the people in irc who definitely could m
by sanderjd 12y ago
As a counter-anecdote, I'm in a very similar boat as the parent comment, and I have been astounded how consistently all the people in irc who definitely could make me feel like an idiot are unwilling to do so. It is a really refreshing experience after years of going into rooms full of arrogant people who actually don't know very much, as opposed to Rust's irc where everyone seems to know everything and are humble nonetheless.
- kibwen 12y agoThis may largely be because we don't actually know everything, thanks to the fact that Rust changes so quickly that even the experts must constantly re-learn the language. :) But I'm very invested in maintaining that atmosphere of respect as we progress towards stability.
- Jemaclus 12y agoI don't disagree! The vast majority of the IRC group was very helpful! I should have mentioned that in my original post. There was just one particular day where I was struggling with a concept and I felt like people were making fun of me and it just really made me not want to touch Rust for a few months. But that's not really the point. I think the point is that there's a need for a sort of onboarding process for people who have never had to deal with some of these basic concepts. For instance, in web development, there's not a lot of need to know much about ownership or memory. The popular languages (Java, PHP, Python) kinda handle those things for you. So when you dig into Rust, you spend a lot of time thinking things like "wtf is a pointer?" and "wtf is a reference?" instead of actually building something useful. That's a really frustrating part for me. I can build anything I want in PHP or Python or Java. I know those languages like the back of my hand, and if you give me a problem, I can solve it. But then I start with a language like Rust, which concerns itself with all kinds of things I've only vaguely heard of, and then I'm completely lost. Super, super, super frustrating. It's a struggle to do a basic blackjack game -- something I could do in my sleep with Python! So you don't know these concepts, which is already frustrating, and then you go into chat and you say "WTF is a pointer?" and hopefully people say "Oh, dude, it's so easy, imagine. you have this..." instead of "That's basic computer science, man. RTFM." To be fair, I think Rust's documentation back at 0.9 was great. I'm positive it's way better now. But back at 0.9, it didn't answer the questions I had, which is why I had to go to chat in the first place. But yes, most people were very, very helpful and I really did learn a lot. :)
- hga 12y agoDoes Wikipedia help, e.g. https://en.wikipedia.org/wiki/Pointer_(computer_programming) https://en.wikipedia.org/wiki/Pointer_(computer_programming) ? I can remember struggling to really learn pointers in C, the key for me was this bit of samizdat: https://en.wikipedia.org/wiki/Lions%27_Commentary_on_UNIX_6th_Edition,_with_Source_Code https://en.wikipedia.org/wiki/Lions%27_Commentary_on_UNIX_6t... So one obvious solution is to annotate a body of real code ... but in general you're suffering from trying to learn a moving target, and good documentation tends to trail.... That Version 6 UNIX(TM) was updated/reimplemented as Xv6 https://en.wikipedia.org/wiki/Xv6 https://en.wikipedia.org/wiki/Xv6 ... maybe someone should do a pedagogical Rust version??? Maybe x86_64 and/or ARM?
- Jemaclus 12y agoYeah, I think the ever-changing nature of Rust was an obstacle, for sure, which is one of the reasons I'm so excited for Rust 1.0. :)
- jimbokun 12y agoIf you're still stuck on pointers (although sounds like you eventually got past it), Kernighan and Ritchie have a very no-nonsense, straightforward presentation of the concept. http://books.cat-v.org/computer-science/c-programming-language/The.C.Programming.Language.2nd.Edition.pdf http://books.cat-v.org/computer-science/c-programming-langua... See chapter 5. Starts with a nice little picture. Of course, the basic concept of a pointer is not really that tricky. It's how to use them, what you can do with them, and how to avoid accidentally shooting off your foot with them that are the tricky parts. Anyhow, if you know any other programmers who want to understand pointers, I don't think you can go too far wrong pointing them towards Kernighan and Ritchie.
- hga 12y agoI, for one, found the arrays and pointers chapter in K&R Edition 1 to be mostly useless (per my other comment in this subthread I used the Lions Notes). Do you know if it was significantly improved in the 2nd Edition you recommend?