4 ms·
You must be a hell of a lot smarter than me: I’ve been hacking rust on the side and it’s taking me like 10x as long at least to do fairly simple things. It’s li
by unsatchmo 8y ago
You must be a hell of a lot smarter than me: I’ve been hacking rust on the side and it’s taking me like 10x as long at least to do fairly simple things. It’s like the crushing burden of choice of C++ paired with the strictness of Haskell. And I’m not sure it’s that much safer than C for low level stuff that requires you to use unsafe anyhow. I’m going to take my kernel project through to programming the MMU, and re-evaluate but it’s slow going man. None of my coworkers would have the patience for this slog.
- bluejekyll 8y agoI hope that you’re using some of the many community resources to help learn. I personally don’t have time to join the IRC channels, but those are great for point in time help, the users forum, stackoverflow, and reddit are all good resources too. Many of the Rust users have all gone through similar learning hurdles, and are very helpful when asked. Often there are tricks that newcomers are unaware of for working around some of the Rust idiosyncrasies. I encourage you to reach out. The official community page has a lot of resources: https://www.rust-lang.org/en-US/community.html https://www.rust-lang.org/en-US/community.html
- dbaupp 8y agoSomewhat surprisingly, you can relatively quickly move from the world of raw pointers and direct hardware interaction to safe abstractions (or at least single-point-of-unsafety, typically on construction, requiring that a pointer points to the right memory-mapped registers, etc). The series written by Phil Opp linked above does a great job of demonstrating this.