"Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless."
If you're doing a lot of work in C/C++/Rust consider using sccache to cache compilations. It's easy to set up and will save you a lot of time and a huge amount of power.
@shram86 this is a generic tool that works with all mainstream compilers and requires just a few lines of global configuration. After that it works completely transparently
https://nexte.st/ is awesome. The expression language to filter for tests or simply display a list of available test made is "must-have" for me. #rustlang#rust
"Note that any lifetime bounds, including 'static, apply only to references and types containing references. They do nothing when applied to self-contained types. This means that String is not 'static, but rather it isn't affected by any lifetime bound."
It's fascinating to me looking at beginning language guides and thinking "what does this say about the culture of the language"
When I was delving into #OCaml it was (with affection) "here's hello world and here's a dense academic paper on implementing event systems in OCaml 5!"
#Java guides used to be centered on the assumption that you were a web programmer looking to do applets, even long after that assumption died.
#RustLang generally seems to assume a background in programming w/ a CLI.
I'll certainly have more observations as I dig more into The Rust Book and Rust by Example on #RustLang, but it is interesting to me to see the baked in assumption that you are pretty comfortable with concepts like package management (I mean Rust By Example talks about creating a library before it talks about using a library and The Rust Book is similar, glossing over nuances here), CLI tools, and build tools.
To be clear, this is all fine, it is just informing me who the target audience is.
After a while with #OCaml my conclusion there is that:
OCaml really is a language for people who are fairly mathy and academic but who still want to get stuff done. The culture felt entirely focused around this question. So you get the dense academic paper not to scare you, but because they think you will be legitimately interested in it (albeit probably not right after hello world, but fairly soon).
OTOH there's a kind of ruthless efficiency: if you need to compromise you compromise.