News for hackers. Stuff that matters.
Re:Rust in 2017: what we achieved by rhexs on Thursday December 21, 2017 @06:14PM (#15983799)
How's the O'Reilly book so far? I made it through the second edition of the rust book but found it a bit lacking as a novice. I think a second time through the Rust book after writing a few programs will be really useful, but I wouldn't mind trying the O'Reilly one as well.
Re:Rust in 2017: what we achieved by pohl on Thursday December 21, 2017 @07:19PM (#15984160)
I’m happy with it. I totally agree with mlevental‘s assessment of the intro. Just getting through that boosted my feeling of competency a lot. I’ve been anticipating this book for a long time, and I’m not disappointed at all.
Re:Rust in 2017: what we achieved by steveklabnik on Thursday December 21, 2017 @06:20PM (#15983837)
I’m pumped to get my paper copy shortly after the new year :)

If you’ve got some time to elaborate on how you struggled with the book, I’d be interested in hearing about it!

Re:Rust in 2017: what we achieved by rhexs on Thursday December 21, 2017 @07:26PM (#15984222)
I think my original statement came off a bit harsh. For more context, I'm a C programmer who managed to avoid C++ and templating for...too long. Rust just has a lot of new (to me) ideas that will probably take a bit longer for me to grasp than other programmers.

As an example, reading the official documentation at first was an absolute struggle due to all the terminology and syntax I was only vaguely familiar from the book. It's getting easier as I practice more.

The more documentation -- the merrier. Thanks a ton for your work!

Re:Rust in 2017: what we achieved by steveklabnik on Thursday December 21, 2017 @09:09PM (#15984734)
Cool cool, no worries. You’re quite welcome!
Re:Rust in 2017: what we achieved by sohkamyung on Thursday December 21, 2017 @07:58PM (#15984407)
I've just started reading it and it looks good. The chapters on ownership and borrowing really clarify how it works in Rust.