←back to thread

452 points birdculture | 1 comments | | HN request time: 0.206s | source
Show context
toprerules ◴[] No.43985668[source]
As a systems programmer I found Rust relatively easy to learn, and wonder if the problem is non-systems programmers trying to learn their first systems language and having it explicitly tell them "no, that's dangerous. no, that doesn't make sense". If you ask a front end developer to suddenly start writing C they are going to create memory leaks, create undefined behavior, create pointers to garbage, run off the end of an array, etc. But they might "feel" like they are doing great because there program compiles and sort of runs.

If you have already gotten to the journeyman or mastery experience level with C or C++ Rust is going to be easy to learn (it was for me). The concepts are simply being made explicit rather than implicit (ownership, lifetimes, traits instead of vtables, etc).

replies(2): >>43987347 #>>43989311 #
1. RealityVoid ◴[] No.43989311[source]
As a low level programmer, my biggest pain with rust was the type system. More precisely the traits and the trait bounds.

I suspect if you have C++ experience it's simpler to grokk, but most of the stuff I wrote was C and a bunch of the stuff Rust did were not familiar to me.