I'm continually delighted to see so many programmers with backgrounds in dynamic languages feeling at home in Rust, given that that's my trajectory as well. :) I'm giving a three-hour Rust tutorial at OSCON this year and I'm honestly torn over whether I should tailor it towards people coming from dynamic langs or people coming from C/C++. I feel like I might end up just having to write two tutorials and take a survey as people come in to determine which to focus on.

As a Rust-curious C++ user, I've actually been frustrated about the lack of C++ to Rust material. It seems easier to find a "Rust for Rubyists" or "Rust from Golang" articles than a "Modern C++ to Rust" guide. In fact the two languages are almost exclusively discussed in a competitive context. This results in a lot of information that isn't really useful to those not emotionally invested in Rust's success.

It's as if folks coming from C++ are supposed to "just get it". It's supposed to be "obvious" why Rust is a better choice than C++, yet I don't see it. Maybe if I was writing some sort of mission-critical software I would look into Rust. But I use C++ for cross-platform mobile applications. I've had trouble finding a compelling reason to invest my precious free time time in learning Rust over furthering my C++14 knowledge.

(I'm not sure how active that is worked on, though, I think I've seen basically the same version back in September.)